2 This document summarizes new features and bugfixes in each stable release
3 of Tor. If you want to see more detailed descriptions of the changes in
4 each development snapshot, see the ChangeLog file.
6 Changes in version 0.2.3.x - 2012-10-??
7 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
10 Tor 0.2.3.x, the first stable release in the 0.2.3 branch, features ...
12 Major features (v3 directory protocol):
13 - Clients now use microdescriptors instead of regular descriptors
14 to build circuits. Microdescriptors are authority-generated
15 summaries of regular descriptors' contents, designed to change very
16 rarely (see proposal 158 for details). This feature is designed
17 to save bandwidth, especially for clients on slow internet
18 connections. Use "UseMicrodescriptors 0" to disable it.
19 - Caches now download, cache, and serve microdescriptors, as well
20 as multiple "flavors" of the consensus, including a flavor that
21 describes microdescriptors.
23 o Major features (build hardening):
24 - Enable gcc and ld hardening by default. Resolves ticket 5210.
26 o Major features (relay scaling):
27 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
28 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
29 vectorized AES implementations as appropriate. These can be much,
30 much faster than other AES implementations.
31 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
32 implementation. It makes AES_CTR about 7% faster than our old one
33 (which was about 10% faster than the one OpenSSL used to provide).
35 - Use OpenSSL's EVP interface for AES encryption, so that all AES
36 operations can use hardware acceleration (if present). Resolves
38 - Unconditionally use OpenSSL's AES implementation instead of our
39 old built-in one. OpenSSL's AES has been better for a while, and
40 relatively few servers should still be on any version of OpenSSL
41 that doesn't have good optimized assembly AES.
43 o Major features (blocking resistance):
44 - Update TLS cipher list to match Firefox 8 and later. Resolves
46 - Remove support for clients falsely claiming to support standard
47 ciphersuites that they can actually provide. As of modern OpenSSL
48 versions, it's not necessary to fake any standard ciphersuite,
49 and doing so prevents us from using better ciphersuites in the
50 future, since servers can't know whether an advertised ciphersuite
51 is really supported or not. Some hosts -- notably, ones with very
52 old versions of OpenSSL or where OpenSSL has been built with ECC
53 disabled -- will stand out because of this change; TBB users should
54 not be affected. Implements the client side of proposal 198.
55 - Implement a new handshake protocol (v3) for authenticating Tors to
56 each other over TLS. It should be more resistant to fingerprinting
57 than previous protocols, and should require less TLS hacking for
58 future Tor implementations. Implements proposal 176.
59 - Allow variable-length padding cells, to disguise the length of
60 Tor's TLS records. Implements part of proposal 184.
61 - While we're trying to bootstrap, record how many TLS connections
62 fail in each state, and report which states saw the most failures
63 in response to any bootstrap failures. This feature may speed up
64 diagnosis of censorship events. Implements ticket 3116.
66 o Major features (pluggable transports):
67 - Clients and bridges can now be configured to use a separate
68 "transport" proxy. This approach makes the censorship arms race
69 easier by allowing bridges to use protocol obfuscation plugins.
70 Implements proposal 180 (tickets 2841 and 3472).
72 o Major features (DoS resistance):
73 - Now that Tor 0.2.0.x is completely deprecated, enable the final
74 part of "Proposal 110: Avoiding infinite length circuits" by
75 refusing all circuit-extend requests that do not use a relay_early
76 cell. This change helps Tor resist a class of denial-of-service
77 attacks by limiting the maximum circuit length.
78 - Tear down the circuit if we get an unexpected SENDME cell. Clients
79 could use this trick to make their circuits receive cells faster
80 than our flow control would have allowed, or to gum up the network,
81 or possibly to do targeted memory denial-of-service attacks on
82 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
83 from July 2002, before the release of Tor 0.0.0.
85 o Major features (hidden services):
86 - Adjust the number of introduction points that a hidden service
87 will try to maintain based on how long its introduction points
88 remain in use and how many introductions they handle. Fixes
90 - Add a "tor2web mode" for clients that want to connect to hidden
91 services non-anonymously (and possibly more quickly). As a safety
92 measure to try to keep users from turning this on without knowing
93 what they are doing, tor2web mode must be explicitly enabled at
94 compile time, and a copy of Tor compiled to run in tor2web mode
95 cannot be used as a normal Tor client. Implements feature 2553.
97 o Major features (IPv6):
98 - Clients can now connect to private bridges over IPv6. Bridges
99 still need at least one IPv4 address in order to connect to
100 other relays. Note that we don't yet handle the case where the
101 user has two bridge lines for the same bridge (one IPv4, one
102 IPv6). Implements parts of proposal 186.
104 o Major features (directory authorities):
105 - Use a more secure consensus parameter voting algorithm. Now at
106 least three directory authorities or a majority of them must
107 vote on a given parameter before it will be included in the
108 consensus. Implements proposal 178.
109 - Remove the artificially low cutoff of 20KB to guarantee the Fast
110 flag. In the past few years the average relay speed has picked
111 up, and while the "top 7/8 of the network get the Fast flag" and
112 "all relays with 20KB or more of capacity get the Fast flag" rules
113 used to have the same result, now the top 7/8 of the network has
114 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
116 o Major features (performance):
117 - Exit nodes now accept and queue data on not-yet-connected streams.
118 Previously, the client wasn't allowed to send data until the
119 stream was connected, which slowed down all connections. This
120 change will enable clients to perform a "fast-start" on streams
121 and send data without having to wait for a confirmation that the
122 stream has opened. Patch from Ian Goldberg; implements the server
123 side of Proposal 174.
124 - When using an exit relay running 0.2.3.x, clients can now
125 "optimistically" send data before the exit relay reports that
126 the stream has opened. This saves a round trip when starting
127 connections where the client speaks first (such as web browsing).
128 This behavior is controlled by a consensus parameter (currently
129 disabled). To turn it on or off manually, use the "OptimisticData"
130 torrc option. Implements proposal 181; code by Ian Goldberg.
131 - Add a new TokenBucketRefillInterval option to refill token buckets
132 more frequently than once per second. This should improve network
133 performance, alleviate queueing problems, and make traffic less
134 bursty. Implements proposal 183; closes ticket 3630. Design by
135 Florian Tschorsch and Björn Scheuermann; implementation by
137 - Raise the threshold of server descriptors needed (75%) and exit
138 server descriptors needed (50%) before we will declare ourselves
139 bootstrapped. This will make clients start building circuits a
140 little later, but makes the initially constructed circuits less
141 skewed and less in conflict with further directory fetches. Fixes
144 o Major features (relays):
145 - Relays now try regenerating and uploading their descriptor more
146 frequently if they are not listed in the consensus, or if the
147 version of their descriptor listed in the consensus is too
148 old. This fix should prevent situations where a server declines
149 to re-publish itself because it has done so too recently, even
150 though the authorities decided not to list its recent-enough
151 descriptor. Fix for bug 3327.
153 o Major features (stream isolation):
154 - You can now configure Tor so that streams from different
155 applications are isolated on different circuits, to prevent an
156 attacker who sees your streams as they leave an exit node from
157 linking your sessions to one another. To do this, choose some way
158 to distinguish the applications: have them connect to different
159 SocksPorts, or have one of them use SOCKS4 while the other uses
160 SOCKS5, or have them pass different authentication strings to the
161 SOCKS proxy. Then, use the new SocksPort syntax to configure the
162 degree of isolation you need. This implements Proposal 171.
163 - There's a new syntax for specifying multiple client ports (such as
164 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
165 multiple *Port entries with full addr:port syntax on each.
166 The old *ListenAddress format is still supported, but you can't
167 mix it with the new *Port syntax.
169 o Major features (bufferevents):
170 - Tor can now optionally build with the "bufferevents" buffered IO
171 backend provided by Libevent 2. To use this feature, make sure you
172 have the latest possible version of Libevent, and pass the
173 --enable-bufferevents flag to configure when building Tor from
174 source. This feature will make our networking code more flexible,
175 let us stack layers on each other, and let us use more efficient
176 zero-copy transports where available.
177 - Add experimental support for running on Windows with IOCP and no
178 kernel-space socket buffers. This feature is controlled by a new
179 "UserspaceIOCPBuffers" config option (off by default), which has
180 no effect unless Tor has been built with bufferevents enabled,
181 you're running on Windows, and you've set "DisableIOCP 0". In the
182 long run, this may help solve or mitigate bug 98.
184 o Major features (path selection):
185 - The EntryNodes option can now include country codes like {de} or IP
186 addresses or network masks. Previously we had disallowed these
187 options because we didn't have an efficient way to keep the list up
188 to date. Addresses ticket 1982, but see bug 2798 for an unresolved
191 o Major features (port forwarding):
192 - Add support for automatic port mapping on the many home routers
193 that support NAT-PMP or UPnP. To build the support code, you'll
194 need to have the libnatpnp library and/or the libminiupnpc library,
195 and you'll need to enable the feature specifically by passing
196 "--enable-upnp" and/or "--enable-natpnp" to ./configure. To turn
197 it on, use the new PortForwarding option.
199 o Major features (logging):
200 - Add a new 'Heartbeat' log message type to periodically log a message
201 describing Tor's status at level Notice. This feature is meant for
202 operators who log at notice, and want to make sure that their Tor
203 server is still working. Implementation by George Kadianakis.
204 - Make logging resolution configurable with a new LogTimeGranularity
205 option, and change the default from 1 millisecond to 1 second.
206 Implements enhancement 1668.
208 o Major features (other):
209 - New "DisableNetwork" config option to prevent Tor from launching any
210 connections or accepting any connections except on a control port.
211 Bundles and controllers can set this option before letting Tor talk
212 to the rest of the network, for example to prevent any connections
213 to a non-bridge address. Packages like Orbot can also use this
214 option to instruct Tor to save power when the network is off.
215 - Try to use system facilities for enumerating local interface
216 addresses, before falling back to our old approach (which was
217 binding a UDP socket, and calling getsockname() on it). That
218 approach was scaring OS X users whose draconian firewall
219 software warned about binding to UDP sockets regardless of
220 whether packets were sent. Now we try to use getifaddrs(),
221 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
222 system supports. Resolves ticket 1827.
223 - Add experimental support for a "defaults" torrc file to be parsed
224 before the regular torrc. Torrc options override the defaults file's
225 options in the same way that the command line overrides the torrc.
226 The SAVECONF controller command saves only those options which
227 differ between the current configuration and the defaults file. HUP
228 reloads both files. Implements task 4552.
230 o Security/privacy fixes:
231 - Avoid read-from-freed-memory and double-free bugs that could occur
232 when a DNS request fails while launching it. Fixes bug 6480;
233 bugfix on 0.2.0.1-alpha.
234 - Reject any attempt to extend to an internal address. Without
235 this fix, a router could be used to probe addresses on an internal
236 network to see whether they were accepting connections. Fixes bug
237 6710; bugfix on 0.0.8pre1.
238 - Close any connection that sends unrecognized junk before the TLS
239 handshake. Solves an issue noted in bug 4369.
240 - The advertised platform of a relay now includes only its operating
241 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not
242 its service pack level (for Windows) or its CPU architecture
243 (for Unix). Also drop the "git-XYZ" tag in the version. Packagers
244 can insert an extra string in the platform line by setting the
245 preprocessor variable TOR_BUILD_TAG. Resolves bug 2988.
247 o Major bugfixes (clients):
248 - If we are unable to find any exit that supports our predicted ports,
249 stop calling them predicted, so that we don't loop and build
250 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
251 which introduced predicted ports.
252 - Check at each new consensus whether our entry guards were picked
253 long enough ago that we should rotate them. Previously, we only
254 did this check at startup, which could lead to us holding a guard
255 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
256 - When fetching a bridge descriptor from a bridge authority,
257 always do so anonymously, whether we have been able to open
258 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
259 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
260 but we'll need to wait for bug 6010 before it's actually usable.
262 o Major bugfixes (directory voting):
263 - Check more thoroughly to prevent a rogue authority from
264 double-voting on any consensus directory parameter. Previously,
265 authorities would crash in this case if the total number of
266 votes for any parameter exceeded the number of active voters,
267 but would let it pass otherwise. Partially fixes bug 5786; bugfix
269 - When computing weight parameters, behave more robustly in the
270 presence of a bad bwweightscale value. Previously, the authorities
271 would crash if they agreed on a sufficiently broken weight_scale
272 value; now, they use a reasonable default and carry on. Fixes the
273 rest of bug 5786; bugfix on 0.2.2.17-alpha.
274 - If authorities are unable to get a v2 consensus document from other
275 directory authorities, they no longer fall back to fetching
276 them from regular directory caches. Fixes bug 5635; bugfix on
277 0.2.2.26-beta, where routers stopped downloading v2 consensus
280 o Major bugfixes (relays):
281 - Fix a bug handling SENDME cells on nonexistent streams that could
282 result in bizarre window values. Report and patch contributed
283 pseudonymously. Fixes part of bug 6271. This bug was introduced
284 before the first Tor release, in svn commit r152.
285 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
286 connections. This change should allow busy exit relays to stop
287 running out of available sockets as quickly. Fixes bug 4950;
288 bugfix on 0.2.2.26-beta.
289 - Don't update the AccountingSoftLimitHitAt state file entry whenever
290 tor gets started. This prevents a wrong average bandwidth
291 estimate, which would cause relays to always start a new accounting
292 interval at the earliest possible moment. Fixes bug 2003; bugfix
293 on 0.2.2.7-alpha. Reported by Bryon Eldridge, who also helped
294 immensely in tracking this bug down.
296 o Major bugfixes (blocking resistance):
297 - Bridges no longer include their address in NETINFO cells on outgoing
298 OR connections, to allow them to blend in better with clients.
299 Removes another avenue for enumerating bridges. Reported by
300 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
301 cells were introduced.
302 - Warn the user when HTTPProxy, but no other proxy type, is
303 configured. This can cause surprising behavior: it doesn't send
304 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
305 directory traffic only. Resolves ticket 4663.
307 o Major bugfixes (hidden services):
308 - Improve hidden service robustness: when an attempt to connect to
309 a hidden service ends, be willing to refetch its hidden service
310 descriptors from each of the HSDir relays responsible for them
311 immediately. Previously, we would not consider refetching the
312 service's descriptors from each HSDir for 15 minutes after the last
313 fetch, which was inconvenient if the hidden service was not running
314 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
315 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
316 They used to check that the timestamp was within 30 minutes
317 of their system clock, so they could cap the size of their
318 replay-detection cache, but that approach unnecessarily refused
319 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
320 the v3 intro-point protocol (the first one which sent a timestamp
321 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
322 - When one of a hidden service's introduction points appears to be
323 unreachable, stop trying it. Previously, we would keep trying
324 to build circuits to the introduction point until we lost the
325 descriptor, usually because the user gave up and restarted Tor.
326 Fixes part of bug 3825.
328 o Changes to default torrc file:
329 - Stop listing "socksport 9050" in torrc.sample. We open a socks
330 port on 9050 by default anyway, so this should not change anything
332 - Stop mentioning the deprecated *ListenAddress options in
333 torrc.sample. Fixes bug 5438.
334 - Document unit of bandwidth-related options in sample torrc.
336 - Fix broken URLs in the sample torrc file, and tell readers about
337 the OutboundBindAddress, ExitPolicyRejectPrivate, and
338 PublishServerDescriptor options. Addresses bug 4652.
340 o Minor features (directory authorities):
341 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
342 change when the authority is deciding whether to accept a newly
343 uploaded descriptor. Implements ticket 6423.
344 - Directory authorities are now a little more lenient at accepting
345 older router descriptors, or newer router descriptors that don't
346 make big changes. This should help ameliorate past and future
347 issues where routers think they have uploaded valid descriptors,
348 but the authorities don't think so. Fix for ticket 2479.
349 - Authority operators can now vote for all relays in a given
350 set of countries to be BadDir/BadExit/Invalid/Rejected.
351 - Provide two consensus parameters (FastFlagMinThreshold and
352 FastFlagMaxThreshold) to control the range of allowable bandwidths
353 for the Fast directory flag. These allow authorities to run
354 experiments on appropriate requirements for being a "Fast" node.
355 The AuthDirFastGuarantee config value still applies. Implements
358 o Minor features (bridges / bridge authorities):
359 - Make bridge SSL certificates a bit more stealthy by using random
360 serial numbers, in the same fashion as OpenSSL when generating
361 self-signed certificates. Implements ticket 4584.
362 - Tag a bridge's descriptor as "never to be sent unencrypted".
363 This shouldn't matter, since bridges don't open non-anonymous
364 connections to the bridge authority and don't allow unencrypted
365 directory connections from clients, but we might as well make
366 sure. Closes bug 5139.
367 - The Bridge Authority now writes statistics on how many bridge
368 descriptors it gave out in total, and how many unique descriptors
369 it gave out. It also lists how often the most and least commonly
370 fetched descriptors were given out, as well as the median and
371 25th/75th percentile. Implements tickets 4200 and 4294.
373 o Minor features (IPv6):
374 - Make the code that clients use to detect an address change be
375 IPv6-aware, so that it won't fill clients' logs with error
376 messages when trying to get the IPv4 address of an IPv6
377 connection. Implements ticket 5537.
378 - Relays now understand an IPv6 address when they get one from a
379 directory server. Resolves ticket 4875.
381 o Minor features (hidden services):
382 - Expire old or over-used hidden service introduction points.
383 Required by fix for bug 3460.
384 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
385 public key replay-detection cache from 60 minutes to 5 minutes. This
386 replay-detection cache is now used only to detect multiple
387 INTRODUCE2 cells specifying the same rendezvous point, so we can
388 avoid launching multiple simultaneous attempts to connect to it.
389 - When a hidden service's introduction point times out, consider
390 trying it again during the next attempt to connect to the
391 HS. Previously, we would not try it again unless a newly fetched
392 descriptor contained it. Required by fixes for bugs 1297 and 3825.
394 o Minor features (relays):
395 - Relays now include a reason for regenerating their descriptors
396 in an HTTP header when uploading to the authorities. This will
397 make it easier to debug descriptor-upload issues in the future.
398 - Turn on directory request statistics by default and include them in
399 extra-info descriptors. Don't break if we have no GeoIP database.
400 - Replace files in stats/ rather than appending to them. Now that we
401 include statistics in extra-info descriptors, it makes no sense to
402 keep old statistics forever. Implements ticket 2930.
403 - Relays that set "ConnDirectionStatistics 1" write statistics on the
404 bidirectional use of connections to disk every 24 hours.
405 - Add a GeoIP file digest to the extra-info descriptor. Implements
408 o Minor features (new config options):
409 - New config option "DynamicDHGroups" (disabled by default) provides
410 each bridge with a unique prime DH modulus to be used during
411 SSL handshakes. This option attempts to help against censors
412 who might use the Apache DH modulus as a static identifier for
413 bridges. Addresses ticket 4548.
414 - New config option "DisableDebuggerAttachment" (on by default)
415 to prevent basic debugging attachment attempts by other processes.
416 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
417 - Ordinarily, Tor does not count traffic from private addresses (like
418 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
419 There is now a new option, CountPrivateBandwidth, to disable this
420 behavior. Patch from Daniel Cagara.
422 o Minor features (different behavior for old config options):
423 - Allow MapAddress directives to specify matches against super-domains,
424 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
425 Implements issue 933.
426 - Don't disable the DirPort when we cannot exceed our AccountingMax
427 limit during this interval because the effective bandwidthrate is
428 low enough. This is useful in a situation where AccountMax is only
429 used as an additional safeguard or to provide statistics.
430 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
431 implements ticket 3439.
432 - When configuring a large set of nodes in EntryNodes, and there are
433 enough of them listed as Guard so that we don't need to consider
434 the non-guard entries, prefer the ones listed with the Guard flag.
435 - If you set the NumCPUs option to 0, Tor will now try to detect how
436 many CPUs you have. This is the new default behavior.
437 - The NodeFamily option -- which let you declare that you want to
438 consider nodes to be part of a family whether they list themselves
439 that way or not -- now allows IP address ranges and country codes.
441 o Minor features (new command-line config behavior):
442 - Slightly change behavior of "list" options (that is, config
443 options that can appear more than once) when they appear both in
444 torrc and on the command line. Previously, the command-line options
445 would be appended to the ones from torrc. Now, the command-line
446 options override the torrc options entirely. This new behavior
447 allows the user to override list options (like exit policies and
448 ports to listen on) from the command line, rather than simply
449 appending to the list.
450 - You can get the old (appending) command-line behavior for "list"
451 options by prefixing the option name with a "+".
452 - You can remove all the values for a "list" option from the command
453 line without adding any new ones by prefixing the option name
456 o Minor features (controller, new events):
457 - Extend the control protocol to report flags that control a circuit's
458 path selection in CIRC events and in replies to 'GETINFO
459 circuit-status'. Implements part of ticket 2411.
460 - Extend the control protocol to report the hidden service address
461 and current state of a hidden-service-related circuit in CIRC
462 events and in replies to 'GETINFO circuit-status'. Implements part
464 - Include the creation time of a circuit in CIRC and CIRC2
465 control-port events and the list produced by the 'GETINFO
466 circuit-status' control-port command.
467 - Add a new CONF_CHANGED event so that controllers can be notified
468 of any configuration changes made by other controllers, or by the
469 user. Implements ticket 1692.
470 - Add a new SIGNAL event to the controller interface so that
471 controllers can be notified when Tor handles a signal. Resolves
472 issue 1955. Patch by John Brooks.
474 o Minor features (controller, new getinfo options):
475 - Expose our view of whether we have gone dormant to the controller,
476 via a new "GETINFO dormant" value. Torbutton and other controllers
477 can use this to avoid doing periodic requests through Tor while
478 it's dormant (bug 4718). Resolves ticket 5954.
479 - Add a new GETINFO option to get total bytes read and written. Patch
480 from pipe, revised by atagar. Resolves ticket 2345.
481 - Implement new GETINFO controller fields to provide information about
482 the Tor process's pid, euid, username, and resource limits.
484 o Minor features (controller, other):
485 - Allow controllers to request an event notification whenever a
486 circuit is cannibalized or its purpose is changed. Implements
488 - Use absolute path names when reporting the torrc filename in the
489 control protocol, so a controller can more easily find the torrc
490 file. Resolves bug 1101.
491 - When reporting the path to the cookie file to the controller,
492 give an absolute path. Resolves ticket 4881.
494 o Minor features (log messages):
495 - Add more information to a log statement that might help track down
496 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
497 non-IP address" messages (or any Bug messages, for that matter!),
498 please let us know about it.
499 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
500 EntryNodes will have no effect. Resolves issue 2571.
501 - Try to make the introductory warning message that Tor prints on
502 startup more useful for actually finding help and information.
503 Resolves ticket 2474.
504 - When the system call to create a listener socket fails, log the
505 error message explaining why. This may help diagnose bug 4027.
507 o Minor features (other):
508 - When we fail to initialize Libevent, retry with IOCP disabled so we
509 don't need to turn on multi-threading support in Libevent, which in
510 turn requires a working socketpair(). This is a workaround for bug
511 4457, which affects Libevent versions from 2.0.1-alpha through
513 - When starting as root and then changing our UID via the User
514 control option, and we have a ControlSocket configured, make sure
515 that the ControlSocket is owned by the same account that Tor will
516 run under. Implements ticket 3421; fix by Jérémy Bobbio.
517 - Accept attempts to include a password authenticator in the
518 handshake, as supported by SOCKS5. This handles SOCKS clients that
519 don't know how to omit a password when authenticating. Resolves
521 - Check for and recover from inconsistency in the microdescriptor
522 cache. This will make it harder for us to accidentally free a
523 microdescriptor without removing it from the appropriate data
524 structures. Fixes issue 3135; issue noted by "wanoskarnet".
525 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
527 o Minor bugfixes (crashes and asserts):
528 - Avoid a pair of double-free and use-after-mark bugs that can
529 occur with certain timings in canceled and re-received DNS
530 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
531 - Fix an assert that directory authorities could trigger on sighup
532 during some configuration state transitions. We now don't treat
533 it as a fatal error when the new descriptor we just generated in
534 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
535 - Avoid segfault when starting up having run with an extremely old
536 version of Tor and parsing its state file. Fixes bug 6801; bugfix
539 o Minor bugfixes (code security):
540 - Prevent a null-pointer dereference when receiving a data cell
541 for a nonexistent stream when the circuit in question has an
542 empty deliver window. We don't believe this is triggerable,
543 since we don't currently allow deliver windows to become empty,
544 but the logic is tricky enough that it's better to make the code
545 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
546 - Fix a (harmless) integer overflow in cell statistics reported by
547 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
548 - Fix our implementation of crypto_random_hostname() so it can't
549 overflow on ridiculously large inputs. (No Tor version has ever
550 provided this kind of bad inputs, but let's be correct in depth.)
551 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
552 - Add a (probably redundant) memory clear between iterations of
553 the router status voting loop, to prevent future coding errors
554 where data might leak between iterations of the loop. Resolves
557 o Minor bugfixes (wrapper functions):
558 - Abort if tor_vasprintf() fails in connection_printf_to_buf() (a
559 utility function used in the control-port code). This shouldn't
560 ever happen unless Tor is completely out of memory, but if it did
561 happen and Tor somehow recovered from it, Tor could have sent a log
562 message to a control port in the middle of a reply to a controller
563 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
564 - Fix some (not actually triggerable) buffer size checks in usage of
565 tor_inet_ntop(). Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
567 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
568 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
569 - Enforce correct return behavior of tor_vsscanf() when the '%%'
570 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
571 - Make our replacement implementation of strtok_r() compatible with
572 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
573 bugfix on 0.2.2.1-alpha.
574 - Find more places in the code that should have been testing for
575 invalid sockets using the SOCKET_OK macro. Required for a fix
576 for bug 4533. Bugfix on 0.2.2.28-beta.
578 o Minor bugfixes (code correctness):
579 - Check return value of fputs() when writing authority certificate
580 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
581 - When building Tor on Windows with -DUNICODE (not default), ensure
582 that error messages, filenames, and DNS server names are always
583 NUL-terminated when we convert them to a single-byte encoding.
584 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
585 - Fix a memory leak when trying to launch a DNS request when the
586 nameservers are unconfigurable. Fixes bug 5916; bugfix on Tor
588 - Make sure to set *socket_error in all error cases in
589 connection_connect(), so it can't produce a warning about
590 errno being zero from errno_to_orconn_end_reason(). Bugfix on
591 0.2.1.1-alpha; resolves ticket 6028.
592 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
593 bug 4532; found by "troll_un".
595 o Minor bugfixes (clients):
596 - Allow one-hop directory-fetching circuits the full "circuit build
597 timeout" period, rather than just half of it, before failing them
598 and marking the relay down. This fix should help reduce cases where
599 clients declare relays (or worse, bridges) unreachable because
600 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
601 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
603 - Ensure we don't cannibalize circuits that are longer than three hops
604 already, so we don't end up making circuits with 5 or more
605 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
606 0.1.0.1-rc which introduced cannibalization.
608 o Minor bugfixes (relays):
609 - Don't publish a new relay descriptor when we reload our onion key,
610 unless the onion key has actually changed. Fixes bug 3263 and
611 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
612 - Exit nodes don't need to fetch certificates for authorities that
613 they don't recognize; only directory authorities, bridges,
614 and caches need to do that. Fixes part of bug 2297; bugfix on
617 o Minor bugfixes (directory authority / mirrors):
618 - Avoid O(n^2) performance characteristics when parsing a large
619 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
620 - Authorities no longer include any router in their microdescriptor
621 consensuses for which they couldn't generate or agree on a
622 microdescriptor. Fixes the second piece of bug 6404; fix on
624 - When checking for requested signatures on the latest consensus
625 before serving it to a client, make sure to check the right
626 consensus flavor. Bugfix on 0.2.2.6-alpha.
627 - Fix an edge case where TestingTorNetwork is set but the authorities
628 and relays all have an uptime of zero, so the private Tor network
629 could briefly lack support for hidden services. Fixes bug 3886;
630 bugfix on 0.2.2.18-alpha.
631 - Directory caches no longer refuse to clean out descriptors because
632 of missing v2 networkstatus documents, unless they're configured
633 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
634 0.2.2.26-beta. Patch by Daniel Bryg.
636 o Minor bugfixes (hidden services):
637 - Don't close hidden service client circuits which have almost
638 finished connecting to their destination when they reach
639 the normal circuit-build timeout. Previously, we would close
640 introduction circuits which are waiting for an acknowledgement
641 from the introduction point, and rendezvous circuits which have
642 been specified in an INTRODUCE1 cell sent to a hidden service,
643 after the normal CBT. Now, we mark them as 'timed out', and launch
644 another rendezvous attempt in parallel. This behavior change can
645 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
646 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
647 - Don't close hidden-service-side rendezvous circuits when they
648 reach the normal circuit-build timeout. This behaviour change can
649 be disabled using the new
650 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
651 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
652 - Assert that hidden-service-related operations are not performed
653 using single-hop circuits. Previously, Tor would assert that
654 client-side streams are not attached to single-hop circuits,
655 but not that other sensitive operations on the client and service
656 side are not performed using single-hop circuits. Fixes bug 3332;
658 - Don't launch more than 10 service-side introduction-point circuits
659 for a hidden service in five minutes. Previously, we would consider
660 launching more introduction-point circuits if at least one second
661 had passed without any introduction-point circuits failing. Fixes
662 bug 4607; bugfix on 0.0.7pre1.
664 o Minor bugfixes (config option behavior):
665 - If the user tries to set MyFamily on a bridge, refuse to
666 do so, and warn about the security implications. Fixes bug 4657;
667 bugfix on 0.2.0.3-alpha.
668 - The "--quiet" and "--hush" options now apply not only to Tor's
669 behavior before logs are configured, but also to Tor's behavior in
670 the absense of configured logs. Fixes bug 3550; bugfix on
672 - Change the AllowDotExit rules so they should actually work.
673 We now enforce AllowDotExit only immediately after receiving an
674 address via SOCKS or DNSPort: other sources are free to provide
675 .exit addresses after the resolution occurs. Fixes bug 3940;
676 bugfix on 0.2.2.1-alpha.
677 - Make "LearnCircuitBuildTimeout 0" work more reliably. Specifically,
678 don't depend on the consensus parameters or compute adaptive
679 timeouts when it is disabled. Fixes bug 5049; bugfix on
681 - After we pick a directory mirror, we would refuse to use it if
682 it's in our ExcludeExitNodes list, resulting in mysterious failures
683 to bootstrap for people who just wanted to avoid exiting from
684 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
685 - When told to add a bridge with the same digest as a preexisting
686 bridge but a different addr:port, change the addr:port as
687 requested. Previously we would not notice the change. Fixes half
688 of bug 5603; fix on 0.2.2.26-beta.
690 o Minor bugfixes (controller):
691 - Allow manual 'authenticate' commands to the controller interface
692 from netcat (nc) as well as telnet. We were rejecting them because
693 they didn't come with the expected whitespace at the end of the
694 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
695 - Report a real bootstrap problem to the controller on router
696 identity mismatch. Previously we just said "foo", which probably
697 made a lot of sense at the time. Fixes bug 4169; bugfix on
699 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
700 option is set to 0 (which Vidalia version 0.2.16 now does when
701 a SAVECONF attempt fails), perform other actions that SIGHUP
702 usually causes (like reopening the logs). Fixes bug 5095; bugfix
704 - Correctly handle checking the permissions on the parent
705 directory of a control socket in the root directory. Bug found
706 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
708 - End AUTHCHALLENGE error messages (in the control protocol) with
709 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36.
711 o Minor bugfixes (network reading/writing):
712 - Disable writing on marked-for-close connections when they are
713 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
714 bug 5263; bugfix on 0.0.2pre13, where we first added a special
715 case for flushing marked connections.
716 - Make sure that there are no unhandled pending TLS errors before
717 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
718 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
719 Bugfix on 0.1.0.5-rc; fixes bug 4528.
720 - Detect SSL handshake even when the initial attempt to write the
721 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
722 - If the client fails to set a reasonable set of ciphersuites
723 during its v2 handshake renegotiation, allow the renegotiation to
724 continue nevertheless (i.e. send all the required certificates).
725 Fixes bug 4591; bugfix on 0.2.0.20-rc.
727 o Minor bugfixes (other):
728 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
729 resource exhaustion, so that clients can adjust their load to
730 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
731 started using END_STREAM_REASON_RESOURCELIMIT.
732 - Don't check for whether the address we're using for outbound
733 connections has changed until after the outbound connection has
734 completed. On Windows, getsockname() doesn't succeed until the
735 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
736 - Don't hold a Windows file handle open for every file mapping;
737 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
739 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
740 bugfix on 0.2.1.10-alpha.
741 - If we fail to write a microdescriptor to the disk cache, do not
742 continue replacing the old microdescriptor file. Fixes bug 2954;
743 bugfix on 0.2.2.6-alpha.
745 o Minor bugfixes (log messages, path selection):
746 - Downgrade "set buildtimeout to low value" messages to "info"
747 severity; they were never an actual problem, there was never
748 anything reasonable to do about them, and they tended to spam logs
749 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
750 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
751 more information to it, so that we can track it down in case it
752 returns again. Mitigates bug 5235.
753 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
754 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
755 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
756 - Issue a notice if a guard completes less than 40% of your circuits.
757 Threshold is configurable by torrc option PathBiasNoticeRate and
758 consensus parameter pb_noticepct. There is additional, off-by-
759 default code to disable guards which fail too many circuits.
760 Addresses ticket 5458.
762 o Minor bugfixes (log messages, client):
763 - Downgrade "Got a certificate, but we already have it" log messages
764 from warning to info, except when we're a dirauth. Fixes bug 5238;
765 bugfix on 0.2.1.7-alpha.
766 - Fix the log message describing how we work around discovering
767 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
768 4837; bugfix on 0.2.2.9-alpha.
769 - When logging about a disallowed .exit name, do not also call it
770 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
771 - Fix a log message suggesting that people contact a non-existent
772 email address. Fixes bug 3448.
773 - Rephrase the log message emitted if the TestSocks check is
774 successful. Patch from Fabian Keil; fixes bug 4094.
775 - Log (at debug level) whenever a circuit's purpose is changed.
776 - Log SSL state transitions at log level DEBUG, log domain
777 HANDSHAKE. This can be useful for debugging censorship events.
778 Implements ticket 3264.
779 - We now log which torrc file we're using on startup. Implements
781 - Rate-limit log messages when asked to connect anonymously to
782 a private address. When these hit, they tended to hit fast and
783 often. Also, don't bother trying to connect to addresses that we
784 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
785 reply makes us think we have been lied to, even when the address the
786 client tried to connect to was "localhost." Resolves ticket 2822.
788 o Minor bugfixes (log messages, non-client):
789 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
790 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
791 - Don't log that we have "decided to publish new relay descriptor"
792 unless we are actually publishing a descriptor. Fixes bug 3942;
793 bugfix on 0.2.2.28-beta.
794 - Log which authority we're missing votes from when we go to fetch
795 them from the other auths.
796 - Replace "Sending publish request" log messages with "Launching
797 upload", so that they no longer confusingly imply that we're
798 sending something to a directory we might not even be connected
799 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
800 - Warn when Tor is configured to use accounting in a way that can
801 link a hidden service to some other hidden service or public
802 address. Resolves ticket 6490.
803 - Fix a minor formatting issue in one of tor-gencert's error messages.
807 - Update to the latest version of the tinytest unit testing framework.
808 This includes a couple of bugfixes that can be relevant for
809 running forked unit tests on Windows, and removes all reserved
811 - Avoid a false positive in the util/threads unit test by increasing
812 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
813 - Make it possible to set the TestingTorNetwork configuration
814 option using AlternateDirAuthority and AlternateBridgeAuthority
815 as an alternative to setting DirServer. Addresses ticket 6377.
816 - Add a unit test for the environment_variable_names_equal() function.
817 - A wide variety of new unit tests by Esteban Manchado Velázquez.
818 - Numerous new unit tests for functions in util.c and address.c by
820 - The long-disabled benchmark tests are now split into their own
821 ./src/test/bench binary.
822 - The benchmark tests can now use more accurate timers than
823 gettimeofday() when such timers are available.
824 - Use tt_assert(), not tor_assert(), for checking for test failures.
825 This makes the unit tests more able to go on in the event that
828 o Build improvements:
829 - Use the dead_strip option when building Tor on OS X. This reduces
830 binary size by almost 19% when linking openssl and libevent
831 statically, which we do for Tor Browser Bundle.
832 - Provide a better error message about possible OSX Asciidoc failure
833 reasons. Fixes bug 6436.
834 - Detect attempts to build Tor on (as yet hypothetical) versions
835 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
836 fix for bug 4533. Bugfix on 0.2.2.28-beta.
837 - On Windows, we now define the _WIN32_WINNT macros only if they
838 are not already defined. This lets the person building Tor decide,
839 if they want, to require a later version of Windows.
840 - Our autogen.sh script now uses autoreconf to launch autoconf,
841 automake, and so on. This is more robust against some of the failure
842 modes associated with running the autotools pieces on their own.
843 - Running "make version" now displays the version of Tor that
844 we're about to build. Idea from katmagic; resolves issue 4400.
845 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
846 on 0.2.2.4-alpha; fixes bug 3427.
847 - New --enable-static-tor configure option for building Tor as
848 statically as possible. Idea, general hackery and thoughts from
849 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
851 - Limited, experimental support for building with nmake and MSVC.
853 o Build requirements:
854 - Building Tor with bufferevent support now requires Libevent
855 2.0.13-stable or later. Previous versions of Libevent had bugs in
856 SSL-related bufferevents and related issues that would make Tor
857 work badly with bufferevents. Requiring 2.0.13-stable also allows
858 Tor with bufferevents to take advantage of Libevent APIs
859 introduced after 2.0.8-rc.
860 - Our build system requires automake 1.6 or later to create the
861 Makefile.in files. Previously, you could have used 1.4.
862 This only affects developers and people building Tor from git;
863 people who build Tor from the source distribution without changing
864 the Makefile.am files should be fine.
865 - Detect when we try to build on a platform that doesn't define
866 AF_UNSPEC to 0. We don't work there, so refuse to compile.
868 o Build fixes (compile/link):
869 - Format more doubles with %f, not %lf. Patch from grarpamp to make
870 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
872 - When building with --enable-static-tor on OpenBSD, do not
873 erroneously attempt to link -lrt. Fixes bug 5103.
874 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
875 that IPv6 stuff will compile on MSVC, and compilation issues
876 will be easier to track down. Fixes bug 5861.
877 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
878 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
879 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
880 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
882 o Build fixes (other):
883 - Use the _WIN32 macro throughout our code to detect Windows.
884 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
886 - Properly handle the case where the build-tree is not the same
887 as the source tree when generating src/common/common_sha1.i,
888 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
889 bugfix on 0.2.0.1-alpha.
890 - During configure, search for library containing cos function as
891 libm lives in libcore on some platforms (BeOS/Haiku). Linking
892 against libm was hard-coded before. Fixes the first part of bug
893 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
895 - Prevent a false positive from the check-spaces script, by disabling
896 the "whitespace between function name and (" check for functions
899 o Packaging (RPM) changes:
900 - Update our default RPM spec files to work with mock and rpmbuild
901 on RHEL/Fedora. They have an updated set of dependencies and
902 conflicts, a fix for an ancient typo when creating the "_tor"
903 user, and better instructions. Thanks to Ondrej Mikle for the
904 patch series. Fixes bug 6043.
905 - On OpenSUSE, create the /var/run/tor directory on startup if it
906 is not already created. Patch from Andreas Stieger. Fixes bug 2573.
908 o Code refactoring (safety):
909 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
910 10 lines. Also, don't nest them. Doing so in the past has
911 led to hard-to-debug code. The new style is to use the
912 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
913 - Use macros to indicate OpenSSL versions, so we don't need to worry
914 about accidental hexadecimal bit shifts.
915 - Use tor_sscanf() in place of scanf() in more places through the
916 code. This makes us a little more locale-independent, and
917 should help shut up code-analysis tools that can't tell
918 a safe sscanf string from a dangerous one.
919 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
920 - Use the smartlist_add_asprintf() alias more consistently.
922 o Code refactoring (consolidate):
923 - A major revision to our internal node-selecting and listing logic.
924 Tor already had at least two major ways to look at the question of
925 "which Tor servers do we know about": a list of router descriptors,
926 and a list of entries in the current consensus. With
927 microdescriptors, we're adding a third. Having so many systems
928 without an abstraction layer over them was hurting the codebase.
929 Now, we have a new "node_t" abstraction that presents a consistent
930 interface to a client's view of a Tor node, and holds (nearly) all
931 of the mutable state formerly in routerinfo_t and routerstatus_t.
932 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
933 Libevent's notion of cached time when possible.
934 - Remove duplicate code for invoking getrlimit() from control.c.
935 - Use OpenSSL's built-in SSL_state_string_long() instead of our
936 own homebrewed ssl_state_to_string() replacement. Patch from
937 Emile Snyder. Fixes bug 4653.
938 - Change the symmetric cipher interface so that creating and
939 initializing a stream cipher are no longer separate functions.
941 o Code refactoring (separate):
942 - Make a new "entry connection" struct as an internal subtype of "edge
943 connection", to simplify the code and make exit connections smaller.
944 - Split connection_about_to_close() into separate functions for each
946 - Rewrite the listener-selection logic so that parsing which ports
947 we want to listen on is now separate from binding to the ports
950 o Code refactoring (name changes):
951 - Rename a handful of old identifiers, mostly related to crypto
952 structures and crypto functions. By convention, our "create an
953 object" functions are called "type_new()", our "free an object"
954 functions are called "type_free()", and our types indicate that
955 they are types only with a final "_t". But a handful of older
956 types and functions broke these rules, with function names like
957 "type_create" or "subsystem_op_type", or with type names like
959 - Rename Tor functions that turn strings into addresses, so that
960 "parse" indicates that no hostname resolution occurs, and
961 "lookup" indicates that hostname resolution may occur. This
962 should help prevent mistakes in the future. Fixes bug 3512.
963 - Use the name "CERTS" consistently to refer to the new cell type;
964 we were calling it CERT in some places and CERTS in others.
965 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
966 invalid value, rather than just -1.
967 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
968 can pick them up when the tests aren't disabled. Bugfix on
969 0.2.2.4-alpha which introduced tinytest.
971 o Code refactoring (other):
972 - Defensively refactor rend_mid_rendezvous() so that protocol
973 violations and length checks happen in the beginning. Fixes
975 - Remove the pure attribute from all functions that used it
976 previously. In many cases we assigned it incorrectly, because the
977 functions might assert or call impure functions, and we don't have
978 evidence that keeping the pure attribute is worthwhile. Implements
979 changes suggested in ticket 4421.
980 - Move the replay-detection cache for the RSA-encrypted parts of
981 INTRODUCE2 cells to the introduction point data structures.
982 Previously, we would use one replay-detection cache per hidden
983 service. Required by fix for bug 3460.
984 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
985 no longer link against Libevent: they never used it, but
986 our library structure used to force them to link it.
988 o Removed features and files:
989 - Remove all internal support for unpadded RSA. We never used it, and
990 it would be a bad idea to start.
991 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
993 - Remove some redundant #include directives throughout the code.
994 Patch from Andrea Gelmini.
995 - Remove some old code to remember statistics about which descriptors
996 we've served as a directory mirror. The feature wasn't used and
997 is outdated now that microdescriptors are around.
998 - Remove some old code to work around even older versions of Tor that
999 used forked processes to handle DNS requests. Such versions of Tor
1000 are no longer in use as relays.
1001 - The "torify" script no longer supports the "tsocks" socksifier
1002 tool, since tsocks doesn't support DNS and UDP right for Tor.
1003 Everyone should be using torsocks instead. Fixes bugs 3530 and
1004 5180. Based on a patch by "ugh".
1005 - Remove the torrc.bridge file: we don't use it for anything, and
1006 it had become badly desynchronized from torrc.sample. Resolves
1010 - Begin a doc/state-contents.txt file to explain the contents of
1011 the Tor state file. Fixes bug 2987.
1012 - Clarify the documentation for the Alternate*Authority options.
1014 - Document the --defaults-torrc option, and the new semantics for
1015 overriding, extending, and clearing lists of options. Closes
1017 - Add missing man page documentation for consensus and microdesc
1018 files. Resolves ticket 6732.
1019 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
1021 o Documentation fixes:
1022 - Improve the manual's documentation for the NT Service command-line
1023 options. Addresses ticket 3964.
1024 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
1025 - Document the changes to the ORPort and DirPort options, and the
1026 fact that {OR/Dir}ListenAddress is now unnecessary (and
1027 therefore deprecated). Resolves ticket 5597.
1028 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
1031 Changes in version 0.2.2.39 - 2012-09-11
1032 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
1036 - Fix an assertion failure in tor_timegm() that could be triggered
1037 by a badly formatted directory object. Bug found by fuzzing with
1038 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
1039 - Do not crash when comparing an address with port value 0 to an
1040 address policy. This bug could have been used to cause a remote
1041 assertion failure by or against directory authorities, or to
1042 allow some applications to crash clients. Fixes bug 6690; bugfix
1046 Changes in version 0.2.2.38 - 2012-08-12
1047 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
1048 attack that could in theory leak path information.
1051 - Avoid an uninitialized memory read when reading a vote or consensus
1052 document that has an unrecognized flavor name. This read could
1053 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
1054 - Try to leak less information about what relays a client is
1055 choosing to a side-channel attacker. Previously, a Tor client would
1056 stop iterating through the list of available relays as soon as it
1057 had chosen one, thus finishing a little earlier when it picked
1058 a router earlier in the list. If an attacker can recover this
1059 timing information (nontrivial but not proven to be impossible),
1060 they could learn some coarse-grained information about which relays
1061 a client was picking (middle nodes in particular are likelier to
1062 be affected than exits). The timing attack might be mitigated by
1063 other factors (see bug 6537 for some discussion), but it's best
1064 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
1067 Changes in version 0.2.2.37 - 2012-06-06
1068 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
1069 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
1073 - Work around a bug in OpenSSL that broke renegotiation with TLS
1074 1.1 and TLS 1.2. Without this workaround, all attempts to speak
1075 the v2 Tor connection protocol when both sides were using OpenSSL
1076 1.0.1 would fail. Resolves ticket 6033.
1077 - When waiting for a client to renegotiate, don't allow it to add
1078 any bytes to the input buffer. This fixes a potential DoS issue.
1079 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
1080 - Fix an edge case where if we fetch or publish a hidden service
1081 descriptor, we might build a 4-hop circuit and then use that circuit
1082 for exiting afterwards -- even if the new last hop doesn't obey our
1083 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
1086 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
1087 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
1090 - Tell GCC and Clang to check for any errors in format strings passed
1091 to the tor_v*(print|scan)f functions.
1094 Changes in version 0.2.2.36 - 2012-05-24
1095 Tor 0.2.2.36 updates the addresses for two of the eight directory
1096 authorities, fixes some potential anonymity and security issues,
1097 and fixes several crash bugs.
1099 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
1100 known flaws, and nobody should be using them. You should upgrade. If
1101 you're using a Linux or BSD and its packages are obsolete, stop using
1102 those packages and upgrade anyway.
1104 o Directory authority changes:
1105 - Change IP address for maatuska (v3 directory authority).
1106 - Change IP address for ides (v3 directory authority), and rename
1110 - When building or running with any version of OpenSSL earlier
1111 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
1112 versions have a bug (CVE-2011-4576) in which their block cipher
1113 padding includes uninitialized data, potentially leaking sensitive
1114 information to any peer with whom they make a SSLv3 connection. Tor
1115 does not use SSL v3 by default, but a hostile client or server
1116 could force an SSLv3 connection in order to gain information that
1117 they shouldn't have been able to get. The best solution here is to
1118 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
1119 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
1120 to make sure that the bug can't happen.
1121 - Never use a bridge or a controller-supplied node as an exit, even
1122 if its exit policy allows it. Found by wanoskarnet. Fixes bug
1123 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
1124 and 0.2.0.3-alpha (for bridge-purpose descriptors).
1125 - Only build circuits if we have a sufficient threshold of the total
1126 descriptors that are marked in the consensus with the "Exit"
1127 flag. This mitigates an attack proposed by wanoskarnet, in which
1128 all of a client's bridges collude to restrict the exit nodes that
1129 the client knows about. Fixes bug 5343.
1130 - Provide controllers with a safer way to implement the cookie
1131 authentication mechanism. With the old method, if another locally
1132 running program could convince a controller that it was the Tor
1133 process, then that program could trick the controller into telling
1134 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
1135 authentication method uses a challenge-response approach to prevent
1136 this attack. Fixes bug 5185; implements proposal 193.
1139 - Avoid logging uninitialized data when unable to decode a hidden
1140 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
1141 - Avoid a client-side assertion failure when receiving an INTRODUCE2
1142 cell on a general purpose circuit. Fixes bug 5644; bugfix on
1144 - Fix builds when the path to sed, openssl, or sha1sum contains
1145 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
1147 - Correct our replacements for the timeradd() and timersub() functions
1148 on platforms that lack them (for example, Windows). The timersub()
1149 function is used when expiring circuits, while timeradd() is
1150 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
1151 bugfix on 0.2.2.24-alpha.
1152 - Fix the SOCKET_OK test that we use to tell when socket
1153 creation fails so that it works on Win64. Fixes part of bug 4533;
1154 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
1157 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
1158 Fixes bug 5346; bugfix on 0.0.8pre3.
1159 - Make our number-parsing functions always treat too-large values
1160 as an error, even when those values exceed the width of the
1161 underlying type. Previously, if the caller provided these
1162 functions with minima or maxima set to the extreme values of the
1163 underlying integer type, these functions would return those
1164 values on overflow rather than treating overflow as an error.
1165 Fixes part of bug 5786; bugfix on 0.0.9.
1166 - Older Linux kernels erroneously respond to strange nmap behavior
1167 by having accept() return successfully with a zero-length
1168 socket. When this happens, just close the connection. Previously,
1169 we would try harder to learn the remote address: but there was
1170 no such remote address to learn, and our method for trying to
1171 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
1172 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
1173 - Correct parsing of certain date types in parse_http_time().
1174 Without this patch, If-Modified-Since would behave
1175 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
1176 Esteban Manchado Velázques.
1177 - Change the BridgePassword feature (part of the "bridge community"
1178 design, which is not yet implemented) to use a time-independent
1179 comparison. The old behavior might have allowed an adversary
1180 to use timing to guess the BridgePassword value. Fixes bug 5543;
1181 bugfix on 0.2.0.14-alpha.
1182 - Detect and reject certain misformed escape sequences in
1183 configuration values. Previously, these values would cause us
1184 to crash if received in a torrc file or over an authenticated
1185 control port. Bug found by Esteban Manchado Velázquez, and
1186 independently by Robert Connolly from Matta Consulting who further
1187 noted that it allows a post-authentication heap overflow. Patch
1188 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
1189 bugfix on 0.2.0.16-alpha.
1190 - Fix a compile warning when using the --enable-openbsd-malloc
1191 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
1192 - During configure, detect when we're building with clang version
1193 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
1194 CFLAGS. clang doesn't support them yet.
1195 - When sending an HTTP/1.1 proxy request, include a Host header.
1196 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
1197 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
1198 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
1199 - If we hit the error case where routerlist_insert() replaces an
1200 existing (old) server descriptor, make sure to remove that
1201 server descriptor from the old_routers list. Fix related to bug
1202 1776. Bugfix on 0.2.2.18-alpha.
1204 o Minor bugfixes (documentation and log messages):
1205 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
1206 Fixes bug 4856; bugfix on Tor 0.0.6.
1207 - Update "ClientOnly" man page entry to explain that there isn't
1208 really any point to messing with it. Resolves ticket 5005.
1209 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
1210 directory authority option (introduced in Tor 0.2.2.34).
1211 - Downgrade the "We're missing a certificate" message from notice
1212 to info: people kept mistaking it for a real problem, whereas it
1213 is seldom the problem even when we are failing to bootstrap. Fixes
1214 bug 5067; bugfix on 0.2.0.10-alpha.
1215 - Correctly spell "connect" in a log message on failure to create a
1216 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
1217 - Clarify the behavior of MaxCircuitDirtiness with hidden service
1218 circuits. Fixes issue 5259.
1221 - Directory authorities now reject versions of Tor older than
1222 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
1223 inclusive. These versions accounted for only a small fraction of
1224 the Tor network, and have numerous known security issues. Resolves
1226 - Update to the May 1 2012 Maxmind GeoLite Country database.
1229 - When sending or relaying a RELAY_EARLY cell, we used to convert
1230 it to a RELAY cell if the connection was using the v1 link
1231 protocol. This was a workaround for older versions of Tor, which
1232 didn't handle RELAY_EARLY cells properly. Now that all supported
1233 versions can handle RELAY_EARLY cells, and now that we're enforcing
1234 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
1235 remove this workaround. Addresses bug 4786.
1238 Changes in version 0.2.2.35 - 2011-12-16
1239 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
1240 buffers code. Absolutely everybody should upgrade.
1242 The bug relied on an incorrect calculation when making data continuous
1243 in one of our IO buffers, if the first chunk of the buffer was
1244 misaligned by just the wrong amount. The miscalculation would allow an
1245 attacker to overflow a piece of heap-allocated memory. To mount this
1246 attack, the attacker would need to either open a SOCKS connection to
1247 Tor's SocksPort (usually restricted to localhost), or target a Tor
1248 instance configured to make its connections through a SOCKS proxy
1249 (which Tor does not do by default).
1251 Good security practice requires that all heap-overflow bugs should be
1252 presumed to be exploitable until proven otherwise, so we are treating
1253 this as a potential code execution attack. Please upgrade immediately!
1254 This bug does not affect bufferevents-based builds of Tor. Special
1255 thanks to "Vektor" for reporting this issue to us!
1257 Tor 0.2.2.35 also fixes several bugs in previous versions, including
1258 crash bugs for unusual configurations, and a long-term bug that
1259 would prevent Tor from starting on Windows machines with draconian
1262 With this release, we remind everyone that 0.2.0.x has reached its
1263 formal end-of-life. Those Tor versions have many known flaws, and
1264 nobody should be using them. You should upgrade -- ideally to the
1265 0.2.2.x series. If you're using a Linux or BSD and its packages are
1266 obsolete, stop using those packages and upgrade anyway.
1268 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
1269 longer receive support after some time in early 2012.
1272 - Fix a heap overflow bug that could occur when trying to pull
1273 data into the first chunk of a buffer, when that chunk had
1274 already had some data drained from it. Fixes CVE-2011-2778;
1275 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
1276 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
1277 that it doesn't attempt to allocate a socketpair. This could cause
1278 some problems on Windows systems with overzealous firewalls. Fix for
1279 bug 4457; workaround for Libevent versions 2.0.1-alpha through
1281 - If we mark an OR connection for close based on a cell we process,
1282 don't process any further cells on it. We already avoid further
1283 reads on marked-for-close connections, but now we also discard the
1284 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
1285 which was the first version where we might mark a connection for
1286 close based on processing a cell on it.
1287 - Correctly sanity-check that we don't underflow on a memory
1288 allocation (and then assert) for hidden service introduction
1289 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
1290 bugfix on 0.2.1.5-alpha.
1291 - Fix a memory leak when we check whether a hidden service
1292 descriptor has any usable introduction points left. Fixes bug
1293 4424. Bugfix on 0.2.2.25-alpha.
1294 - Don't crash when we're running as a relay and don't have a GeoIP
1295 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
1296 we've had in the 0.2.3.x branch already.
1297 - When running as a client, do not print a misleading (and plain
1298 wrong) log message that we're collecting "directory request"
1299 statistics: clients don't collect statistics. Also don't create a
1300 useless (because empty) stats file in the stats/ directory. Fixes
1301 bug 4353; bugfix on 0.2.2.34.
1304 - Detect failure to initialize Libevent. This fix provides better
1305 detection for future instances of bug 4457.
1306 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
1307 function. This was eating up hideously large amounts of time on some
1308 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
1309 - Resolve an integer overflow bug in smartlist_ensure_capacity().
1310 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
1312 - Don't warn about unused log_mutex in log.c when building with
1313 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
1314 0.1.0.6-rc which introduced --disable-threads.
1315 - When configuring, starting, or stopping an NT service, stop
1316 immediately after the service configuration attempt has succeeded
1317 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
1318 - When sending a NETINFO cell, include the original address
1319 received for the other side, not its canonical address. Found
1320 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
1321 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
1322 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
1323 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
1324 occurred when a client tried to fetch a descriptor for a bridge
1325 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
1326 - Backport fixes for a pair of compilation warnings on Windows.
1327 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
1328 - If we had ever tried to call tor_addr_to_str on an address of
1329 unknown type, we would have done a strdup on an uninitialized
1330 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
1331 Reported by "troll_un".
1332 - Correctly detect and handle transient lookup failures from
1333 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
1334 Reported by "troll_un".
1335 - Fix null-pointer access that could occur if TLS allocation failed.
1336 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
1337 - Use tor_socket_t type for listener argument to accept(). Fixes bug
1338 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
1341 - Add two new config options for directory authorities:
1342 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
1343 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
1344 that is always sufficient to satisfy the bandwidth requirement for
1345 the Guard flag. Now it will be easier for researchers to simulate
1346 Tor networks with different values. Resolves ticket 4484.
1347 - When Tor ignores a hidden service specified in its configuration,
1348 include the hidden service's directory in the warning message.
1349 Previously, we would only tell the user that some hidden service
1350 was ignored. Bugfix on 0.0.6; fixes bug 4426.
1351 - Update to the December 6 2011 Maxmind GeoLite Country database.
1353 o Packaging changes:
1354 - Make it easier to automate expert package builds on Windows,
1355 by removing an absolute path from makensis.exe command.
1358 Changes in version 0.2.2.34 - 2011-10-26
1359 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
1360 can deanonymize Tor users. Everybody should upgrade.
1362 The attack relies on four components: 1) Clients reuse their TLS cert
1363 when talking to different relays, so relays can recognize a user by
1364 the identity key in her cert. 2) An attacker who knows the client's
1365 identity key can probe each guard relay to see if that identity key
1366 is connected to that guard relay right now. 3) A variety of active
1367 attacks in the literature (starting from "Low-Cost Traffic Analysis
1368 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
1369 discover the guard relays that a Tor user visiting the website is using.
1370 4) Clients typically pick three guards at random, so the set of guards
1371 for a given user could well be a unique fingerprint for her. This
1372 release fixes components #1 and #2, which is enough to block the attack;
1373 the other two remain as open research problems. Special thanks to
1374 "frosty_un" for reporting the issue to us!
1376 Clients should upgrade so they are no longer recognizable by the TLS
1377 certs they present. Relays should upgrade so they no longer allow a
1378 remote attacker to probe them to test whether unpatched clients are
1379 currently connected to them.
1381 This release also fixes several vulnerabilities that allow an attacker
1382 to enumerate bridge relays. Some bridge enumeration attacks still
1383 remain; see for example proposal 188.
1385 o Privacy/anonymity fixes (clients):
1386 - Clients and bridges no longer send TLS certificate chains on
1387 outgoing OR connections. Previously, each client or bridge would
1388 use the same cert chain for all outgoing OR connections until
1389 its IP address changes, which allowed any relay that the client
1390 or bridge contacted to determine which entry guards it is using.
1391 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
1392 - If a relay receives a CREATE_FAST cell on a TLS connection, it
1393 no longer considers that connection as suitable for satisfying a
1394 circuit EXTEND request. Now relays can protect clients from the
1395 CVE-2011-2768 issue even if the clients haven't upgraded yet.
1396 - Directory authorities no longer assign the Guard flag to relays
1397 that haven't upgraded to the above "refuse EXTEND requests
1398 to client connections" fix. Now directory authorities can
1399 protect clients from the CVE-2011-2768 issue even if neither
1400 the clients nor the relays have upgraded yet. There's a new
1401 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
1402 to let us transition smoothly, else tomorrow there would be no
1405 o Privacy/anonymity fixes (bridge enumeration):
1406 - Bridge relays now do their directory fetches inside Tor TLS
1407 connections, like all the other clients do, rather than connecting
1408 directly to the DirPort like public relays do. Removes another
1409 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
1410 - Bridges relays now build circuits for themselves in a more similar
1411 way to how clients build them. Removes another avenue for
1412 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
1413 when bridges were introduced.
1414 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
1415 that they initiated. Relays could distinguish incoming bridge
1416 connections from client connections, creating another avenue for
1417 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
1418 Found by "frosty_un".
1421 - Fix a crash bug when changing node restrictions while a DNS lookup
1422 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
1424 - Don't launch a useless circuit after failing to use one of a
1425 hidden service's introduction points. Previously, we would
1426 launch a new introduction circuit, but not set the hidden service
1427 which that circuit was intended to connect to, so it would never
1428 actually be used. A different piece of code would then create a
1429 new introduction circuit correctly. Bug reported by katmagic and
1430 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
1433 - Change an integer overflow check in the OpenBSD_Malloc code so
1434 that GCC is less likely to eliminate it as impossible. Patch
1435 from Mansour Moufid. Fixes bug 4059.
1436 - When a hidden service turns an extra service-side introduction
1437 circuit into a general-purpose circuit, free the rend_data and
1438 intro_key fields first, so we won't leak memory if the circuit
1439 is cannibalized for use as another service-side introduction
1440 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
1441 - Bridges now skip DNS self-tests, to act a little more stealthily.
1442 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
1443 bridges. Patch by "warms0x".
1444 - Fix internal bug-checking logic that was supposed to catch
1445 failures in digest generation so that it will fail more robustly
1446 if we ask for a nonexistent algorithm. Found by Coverity Scan.
1447 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
1448 - Report any failure in init_keys() calls launched because our
1449 IP address has changed. Spotted by Coverity Scan. Bugfix on
1450 0.1.1.4-alpha; fixes CID 484.
1452 o Minor bugfixes (log messages and documentation):
1453 - Remove a confusing dollar sign from the example fingerprint in the
1454 man page, and also make the example fingerprint a valid one. Fixes
1455 bug 4309; bugfix on 0.2.1.3-alpha.
1456 - The next version of Windows will be called Windows 8, and it has
1457 a major version of 6, minor version of 2. Correctly identify that
1458 version instead of calling it "Very recent version". Resolves
1459 ticket 4153; reported by funkstar.
1460 - Downgrade log messages about circuit timeout calibration from
1461 "notice" to "info": they don't require or suggest any human
1462 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
1463 bugfix on 0.2.2.14-alpha.
1466 - Turn on directory request statistics by default and include them in
1467 extra-info descriptors. Don't break if we have no GeoIP database.
1468 Backported from 0.2.3.1-alpha; implements ticket 3951.
1469 - Update to the October 4 2011 Maxmind GeoLite Country database.
1472 Changes in version 0.2.1.31 - 2011-10-26
1473 Tor 0.2.1.31 backports important security and privacy fixes for
1474 oldstable. This release is intended only for package maintainers and
1475 others who cannot use the 0.2.2 stable series. All others should be
1476 using Tor 0.2.2.x or newer.
1478 o Security fixes (also included in 0.2.2.x):
1479 - Replace all potentially sensitive memory comparison operations
1480 with versions whose runtime does not depend on the data being
1481 compared. This will help resist a class of attacks where an
1482 adversary can use variations in timing information to learn
1483 sensitive data. Fix for one case of bug 3122. (Safe memcmp
1484 implementation by Robert Ransom based partially on code by DJB.)
1485 - Fix an assert in parsing router descriptors containing IPv6
1486 addresses. This one took down the directory authorities when
1487 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
1489 o Privacy/anonymity fixes (also included in 0.2.2.x):
1490 - Clients and bridges no longer send TLS certificate chains on
1491 outgoing OR connections. Previously, each client or bridge would
1492 use the same cert chain for all outgoing OR connections until
1493 its IP address changes, which allowed any relay that the client
1494 or bridge contacted to determine which entry guards it is using.
1495 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
1496 - If a relay receives a CREATE_FAST cell on a TLS connection, it
1497 no longer considers that connection as suitable for satisfying a
1498 circuit EXTEND request. Now relays can protect clients from the
1499 CVE-2011-2768 issue even if the clients haven't upgraded yet.
1500 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
1501 that they initiated. Relays could distinguish incoming bridge
1502 connections from client connections, creating another avenue for
1503 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
1504 Found by "frosty_un".
1505 - When receiving a hidden service descriptor, check that it is for
1506 the hidden service we wanted. Previously, Tor would store any
1507 hidden service descriptors that a directory gave it, whether it
1508 wanted them or not. This wouldn't have let an attacker impersonate
1509 a hidden service, but it did let directories pre-seed a client
1510 with descriptors that it didn't want. Bugfix on 0.0.6.
1511 - Avoid linkability based on cached hidden service descriptors: forget
1512 all hidden service descriptors cached as a client when processing a
1513 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
1514 - Make the bridge directory authority refuse to answer directory
1515 requests for "all" descriptors. It used to include bridge
1516 descriptors in its answer, which was a major information leak.
1517 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
1518 - Don't attach new streams to old rendezvous circuits after SIGNAL
1519 NEWNYM. Previously, we would keep using an existing rendezvous
1520 circuit if it remained open (i.e. if it were kept open by a
1521 long-lived stream, or if a new stream were attached to it before
1522 Tor could notice that it was old and no longer in use). Bugfix on
1523 0.1.1.15-rc; fixes bug 3375.
1525 o Minor bugfixes (also included in 0.2.2.x):
1526 - When we restart our relay, we might get a successful connection
1527 from the outside before we've started our reachability tests,
1528 triggering a warning: "ORPort found reachable, but I have no
1529 routerinfo yet. Failing to inform controller of success." This
1530 bug was harmless unless Tor is running under a controller
1531 like Vidalia, in which case the controller would never get a
1532 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
1534 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
1535 enabled. Fixes bug 1526.
1536 - Remove undocumented option "-F" from tor-resolve: it hasn't done
1537 anything since 0.2.1.16-rc.
1538 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
1539 None of the cases where we did this before were wrong, but by making
1540 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
1541 - Fix a rare crash bug that could occur when a client was configured
1542 with a large number of bridges. Fixes bug 2629; bugfix on
1543 0.2.1.2-alpha. Bugfix by trac user "shitlei".
1544 - Correct the warning displayed when a rendezvous descriptor exceeds
1545 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
1547 - Fix an uncommon assertion failure when running with DNSPort under
1548 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
1549 - When warning about missing zlib development packages during compile,
1550 give the correct package names. Bugfix on 0.2.0.1-alpha.
1551 - Require that introduction point keys and onion keys have public
1552 exponent 65537. Bugfix on 0.2.0.10-alpha.
1553 - Do not crash when our configuration file becomes unreadable, for
1554 example due to a permissions change, between when we start up
1555 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
1557 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
1559 - Always NUL-terminate the sun_path field of a sockaddr_un before
1560 passing it to the kernel. (Not a security issue: kernels are
1561 smart enough to reject bad sockaddr_uns.) Found by Coverity;
1562 CID #428. Bugfix on Tor 0.2.0.3-alpha.
1563 - Don't stack-allocate the list of supplementary GIDs when we're
1564 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
1565 could take up to 256K, which is way too much stack. Found by
1566 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
1568 o Minor bugfixes (only in 0.2.1.x):
1569 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
1570 rely on them. Bugfix on 0.2.1.30.
1571 - Use git revisions instead of svn revisions when generating our
1572 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
1574 o Minor features (also included in 0.2.2.x):
1575 - Adjust the expiration time on our SSL session certificates to
1576 better match SSL certs seen in the wild. Resolves ticket 4014.
1577 - Allow nameservers with IPv6 address. Resolves bug 2574.
1578 - Update to the October 4 2011 Maxmind GeoLite Country database.
1581 Changes in version 0.2.2.33 - 2011-09-13
1582 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
1583 TLS handshake that makes relays and bridges that run this new version
1584 reachable from Iran again.
1587 - Avoid an assertion failure when reloading a configuration with
1588 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
1589 3923; bugfix on 0.2.2.25-alpha.
1591 o Minor features (security):
1592 - Check for replays of the public-key encrypted portion of an
1593 INTRODUCE1 cell, in addition to the current check for replays of
1594 the g^x value. This prevents a possible class of active attacks
1595 by an attacker who controls both an introduction point and a
1596 rendezvous point, and who uses the malleability of AES-CTR to
1597 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
1598 that these attacks are infeasible (requiring the attacker to send
1599 on the order of zettabytes of altered cells in a short interval),
1600 but we'd rather block them off in case there are any classes of
1601 this attack that we missed. Reported by Willem Pinckaers.
1604 - Adjust the expiration time on our SSL session certificates to
1605 better match SSL certs seen in the wild. Resolves ticket 4014.
1606 - Change the default required uptime for a relay to be accepted as
1607 a HSDir (hidden service directory) from 24 hours to 25 hours.
1608 Improves on 0.2.0.10-alpha; resolves ticket 2649.
1609 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
1610 authorities to abstain from voting on assignment of the HSDir
1611 consensus flag. Related to bug 2649.
1612 - Update to the September 6 2011 Maxmind GeoLite Country database.
1614 o Minor bugfixes (documentation and log messages):
1615 - Correct the man page to explain that HashedControlPassword and
1616 CookieAuthentication can both be set, in which case either method
1617 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
1618 when we decided to allow these config options to both be set. Issue
1620 - Demote the 'replay detected' log message emitted when a hidden
1621 service receives the same Diffie-Hellman public key in two different
1622 INTRODUCE2 cells to info level. A normal Tor client can cause that
1623 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
1624 fixes part of bug 2442.
1625 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
1626 level. There is nothing that a hidden service's operator can do
1627 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
1629 - Clarify a log message specifying the characters permitted in
1630 HiddenServiceAuthorizeClient client names. Previously, the log
1631 message said that "[A-Za-z0-9+-_]" were permitted; that could have
1632 given the impression that every ASCII character between "+" and "_"
1633 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
1636 - Provide a substitute implementation of lround() for MSVC, which
1637 apparently lacks it. Patch from Gisle Vanem.
1638 - Clean up some code issues that prevented Tor from building on older
1639 BSDs. Fixes bug 3894; reported by "grarpamp".
1640 - Search for a platform-specific version of "ar" when cross-compiling.
1641 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
1644 Changes in version 0.2.2.32 - 2011-08-27
1645 The Tor 0.2.2 release series is dedicated to the memory of Andreas
1646 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
1647 a founder of the PETS community, a leader in our field, a mentor,
1648 and a friend. He left us with these words: "I had the possibility
1649 to contribute to this world that is not as it should be. I hope I
1650 could help in some areas to make the world a better place, and that
1651 I could also encourage other people to be engaged in improving the
1652 world. Please, stay engaged. This world needs you, your love, your
1653 initiative -- now I cannot be part of that anymore."
1655 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
1656 ready. More than two years in the making, this release features improved
1657 client performance and hidden service reliability, better compatibility
1658 for Android, correct behavior for bridges that listen on more than
1659 one address, more extensible and flexible directory object handling,
1660 better reporting of network statistics, improved code security, and
1661 many many other features and bugfixes.
1663 o Major features (client performance):
1664 - When choosing which cells to relay first, relays now favor circuits
1665 that have been quiet recently, to provide lower latency for
1666 low-volume circuits. By default, relays enable or disable this
1667 feature based on a setting in the consensus. They can override
1668 this default by using the new "CircuitPriorityHalflife" config
1669 option. Design and code by Ian Goldberg, Can Tang, and Chris
1671 - Directory authorities now compute consensus weightings that instruct
1672 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
1673 and no flag. Clients use these weightings to distribute network load
1674 more evenly across these different relay types. The weightings are
1675 in the consensus so we can change them globally in the future. Extra
1676 thanks to "outofwords" for finding some nasty security bugs in
1677 the first implementation of this feature.
1679 o Major features (client performance, circuit build timeout):
1680 - Tor now tracks how long it takes to build client-side circuits
1681 over time, and adapts its timeout to local network performance.
1682 Since a circuit that takes a long time to build will also provide
1683 bad performance, we get significant latency improvements by
1684 discarding the slowest 20% of circuits. Specifically, Tor creates
1685 circuits more aggressively than usual until it has enough data
1686 points for a good timeout estimate. Implements proposal 151.
1687 - Circuit build timeout constants can be controlled by consensus
1688 parameters. We set good defaults for these parameters based on
1689 experimentation on broadband and simulated high-latency links.
1690 - Circuit build time learning can be disabled via consensus parameter
1691 or by the client via a LearnCircuitBuildTimeout config option. We
1692 also automatically disable circuit build time calculation if either
1693 AuthoritativeDirectory is set, or if we fail to write our state
1694 file. Implements ticket 1296.
1696 o Major features (relays use their capacity better):
1697 - Set SO_REUSEADDR socket option on all sockets, not just
1698 listeners. This should help busy exit nodes avoid running out of
1699 useable ports just because all the ports have been used in the
1700 near past. Resolves issue 2850.
1701 - Relays now save observed peak bandwidth throughput rates to their
1702 state file (along with total usage, which was already saved),
1703 so that they can determine their correct estimated bandwidth on
1704 restart. Resolves bug 1863, where Tor relays would reset their
1705 estimated bandwidth to 0 after restarting.
1706 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
1707 should give us approximately 40-50% more Guard-flagged nodes,
1708 improving the anonymity the Tor network can provide and also
1709 decreasing the dropoff in throughput that relays experience when
1710 they first get the Guard flag.
1711 - Directory authorities now take changes in router IP address and
1712 ORPort into account when determining router stability. Previously,
1713 if a router changed its IP or ORPort, the authorities would not
1714 treat it as having any downtime for the purposes of stability
1715 calculation, whereas clients would experience downtime since the
1716 change would take a while to propagate to them. Resolves issue 1035.
1717 - New AccelName and AccelDir options add support for dynamic OpenSSL
1718 hardware crypto acceleration engines.
1720 o Major features (relays control their load better):
1721 - Exit relays now try harder to block exit attempts from unknown
1722 relays, to make it harder for people to use them as one-hop proxies
1723 a la tortunnel. Controlled by the refuseunknownexits consensus
1724 parameter (currently enabled), or you can override it on your
1725 relay with the RefuseUnknownExits torrc option. Resolves bug 1751;
1726 based on a variant of proposal 163.
1727 - Add separate per-conn write limiting to go with the per-conn read
1728 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
1729 but never per-conn write limits.
1730 - New consensus params "bwconnrate" and "bwconnburst" to let us
1731 rate-limit client connections as they enter the network. It's
1732 controlled in the consensus so we can turn it on and off for
1733 experiments. It's starting out off. Based on proposal 163.
1735 o Major features (controllers):
1736 - Export GeoIP information on bridge usage to controllers even if we
1737 have not yet been running for 24 hours. Now Vidalia bridge operators
1738 can get more accurate and immediate feedback about their
1739 contributions to the network.
1740 - Add an __OwningControllerProcess configuration option and a
1741 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
1742 that when it exits, Tor will shut down. Implements feature 3049.
1744 o Major features (directory authorities):
1745 - Directory authorities now create, vote on, and serve multiple
1746 parallel formats of directory data as part of their voting process.
1747 Partially implements Proposal 162: "Publish the consensus in
1749 - Directory authorities now agree on and publish small summaries
1750 of router information that clients can use in place of regular
1751 server descriptors. This transition will allow Tor 0.2.3 clients
1752 to use far less bandwidth for downloading information about the
1753 network. Begins the implementation of Proposal 158: "Clients
1754 download consensus + microdescriptors".
1755 - The directory voting system is now extensible to use multiple hash
1756 algorithms for signatures and resource selection. Newer formats
1757 are signed with SHA256, with a possibility for moving to a better
1758 hash algorithm in the future.
1759 - Directory authorities can now vote on arbitary integer values as
1760 part of the consensus process. This is designed to help set
1761 network-wide parameters. Implements proposal 167.
1763 o Major features and bugfixes (node selection):
1764 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
1765 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and Strict*Nodes
1766 options. Previously, we had been ambiguous in describing what
1767 counted as an "exit" node, and what operations exactly "StrictNodes
1768 0" would permit. This created confusion when people saw nodes built
1769 through unexpected circuits, and made it hard to tell real bugs from
1770 surprises. Now the intended behavior is:
1771 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
1772 a node that delivers user traffic outside the Tor network.
1773 . "Entry", in the context of EntryNodes, means a node used as the
1774 first hop of a multihop circuit. It doesn't include direct
1775 connections to directory servers.
1776 . "ExcludeNodes" applies to all nodes.
1777 . "StrictNodes" changes the behavior of ExcludeNodes only. When
1778 StrictNodes is set, Tor should avoid all nodes listed in
1779 ExcludeNodes, even when it will make user requests fail. When
1780 StrictNodes is *not* set, then Tor should follow ExcludeNodes
1781 whenever it can, except when it must use an excluded node to
1782 perform self-tests, connect to a hidden service, provide a
1783 hidden service, fulfill a .exit request, upload directory
1784 information, or fetch directory information.
1785 Collectively, the changes to implement the behavior fix bug 1090.
1786 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
1787 change during a config reload, mark and discard all our origin
1788 circuits. This fix should address edge cases where we change the
1789 config options and but then choose a circuit that we created before
1791 - Make EntryNodes config option much more aggressive even when
1792 StrictNodes is not set. Before it would prepend your requested
1793 entrynodes to your list of guard nodes, but feel free to use others
1794 after that. Now it chooses only from your EntryNodes if any of
1795 those are available, and only falls back to others if a) they're
1796 all down and b) StrictNodes is not set.
1797 - Now we refresh your entry guards from EntryNodes at each consensus
1798 fetch -- rather than just at startup and then they slowly rot as
1799 the network changes.
1800 - Add support for the country code "{??}" in torrc options like
1801 ExcludeNodes, to indicate all routers of unknown country. Closes
1803 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
1804 a node is listed in both, it's treated as excluded.
1805 - ExcludeNodes now applies to directory nodes -- as a preference if
1806 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
1807 Don't exclude all the directory authorities and set StrictNodes to 1
1808 unless you really want your Tor to break.
1809 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
1810 - ExcludeExitNodes now overrides .exit requests.
1811 - We don't use bridges listed in ExcludeNodes.
1812 - When StrictNodes is 1:
1813 . We now apply ExcludeNodes to hidden service introduction points
1814 and to rendezvous points selected by hidden service users. This
1815 can make your hidden service less reliable: use it with caution!
1816 . If we have used ExcludeNodes on ourself, do not try relay
1817 reachability self-tests.
1818 . If we have excluded all the directory authorities, we will not
1819 even try to upload our descriptor if we're a relay.
1820 . Do not honor .exit requests to an excluded node.
1821 - When the set of permitted nodes changes, we now remove any mappings
1822 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
1824 - We never cannibalize a circuit that had excluded nodes on it, even
1825 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
1826 - Improve log messages related to excluded nodes.
1828 o Major features (misc):
1829 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
1830 to help Tor build correctly for Android phones.
1831 - The options SocksPort, ControlPort, and so on now all accept a
1832 value "auto" that opens a socket on an OS-selected port. A
1833 new ControlPortWriteToFile option tells Tor to write its
1834 actual control port or ports to a chosen file. If the option
1835 ControlPortFileGroupReadable is set, the file is created as
1836 group-readable. Now users can run two Tor clients on the same
1837 system without needing to manually mess with parameters. Resolves
1838 part of ticket 3076.
1839 - Tor now supports tunneling all of its outgoing connections over
1840 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
1841 configuration options. Code by Christopher Davis.
1843 o Code security improvements:
1844 - Replace all potentially sensitive memory comparison operations
1845 with versions whose runtime does not depend on the data being
1846 compared. This will help resist a class of attacks where an
1847 adversary can use variations in timing information to learn
1848 sensitive data. Fix for one case of bug 3122. (Safe memcmp
1849 implementation by Robert Ransom based partially on code by DJB.)
1850 - Enable Address Space Layout Randomization (ASLR) and Data Execution
1851 Prevention (DEP) by default on Windows to make it harder for
1852 attackers to exploit vulnerabilities. Patch from John Brooks.
1853 - New "--enable-gcc-hardening" ./configure flag (off by default)
1854 to turn on gcc compile time hardening options. It ensures
1855 that signed ints have defined behavior (-fwrapv), enables
1856 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
1857 with canaries (-fstack-protector-all), turns on ASLR protection if
1858 supported by the kernel (-fPIE, -pie), and adds additional security
1859 related warnings. Verified to work on Mac OS X and Debian Lenny.
1860 - New "--enable-linker-hardening" ./configure flag (off by default)
1861 to turn on ELF specific hardening features (relro, now). This does
1862 not work with Mac OS X or any other non-ELF binary format.
1863 - Always search the Windows system directory for system DLLs, and
1864 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
1865 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
1866 current and future memory pages via mlockall(). On supported
1867 platforms (modern Linux and probably BSD but not Windows or OS X),
1868 this should effectively disable any and all attempts to page out
1869 memory. This option requires that you start your Tor as root --
1870 if you use DisableAllSwap, please consider using the User option
1871 to properly reduce the privileges of your Tor.
1873 o Major bugfixes (crashes):
1874 - Fix crash bug on platforms where gmtime and localtime can return
1875 NULL. Windows 7 users were running into this one. Fixes part of bug
1876 2077. Bugfix on all versions of Tor. Found by boboper.
1877 - Introduce minimum/maximum values that clients will believe
1878 from the consensus. Now we'll have a better chance to avoid crashes
1879 or worse when a consensus param has a weird value.
1880 - Fix a rare crash bug that could occur when a client was configured
1881 with a large number of bridges. Fixes bug 2629; bugfix on
1882 0.2.1.2-alpha. Bugfix by trac user "shitlei".
1883 - Do not crash when our configuration file becomes unreadable, for
1884 example due to a permissions change, between when we start up
1885 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
1887 - If we're in the pathological case where there's no exit bandwidth
1888 but there is non-exit bandwidth, or no guard bandwidth but there
1889 is non-guard bandwidth, don't crash during path selection. Bugfix
1891 - Fix a crash bug when trying to initialize the evdns module in
1892 Libevent 2. Bugfix on 0.2.1.16-rc.
1894 o Major bugfixes (stability):
1895 - Fix an assert in parsing router descriptors containing IPv6
1896 addresses. This one took down the directory authorities when
1897 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
1898 - Fix an uncommon assertion failure when running with DNSPort under
1899 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
1900 - Treat an unset $HOME like an empty $HOME rather than triggering an
1901 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
1902 - More gracefully handle corrupt state files, removing asserts
1903 in favor of saving a backup and resetting state.
1904 - Instead of giving an assertion failure on an internal mismatch
1905 on estimated freelist size, just log a BUG warning and try later.
1906 Mitigates but does not fix bug 1125.
1907 - Fix an assert that got triggered when using the TestingTorNetwork
1908 configuration option and then issuing a GETINFO config-text control
1909 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
1910 - If the cached cert file is unparseable, warn but don't exit.
1912 o Privacy fixes (relays/bridges):
1913 - Don't list Windows capabilities in relay descriptors. We never made
1914 use of them, and maybe it's a bad idea to publish them. Bugfix
1916 - If the Nickname configuration option isn't given, Tor would pick a
1917 nickname based on the local hostname as the nickname for a relay.
1918 Because nicknames are not very important in today's Tor and the
1919 "Unnamed" nickname has been implemented, this is now problematic
1920 behavior: It leaks information about the hostname without being
1921 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
1922 introduced the Unnamed nickname. Reported by tagnaq.
1923 - Maintain separate TLS contexts and certificates for incoming and
1924 outgoing connections in bridge relays. Previously we would use the
1925 same TLS contexts and certs for incoming and outgoing connections.
1926 Bugfix on 0.2.0.3-alpha; addresses bug 988.
1927 - Maintain separate identity keys for incoming and outgoing TLS
1928 contexts in bridge relays. Previously we would use the same
1929 identity keys for incoming and outgoing TLS contexts. Bugfix on
1930 0.2.0.3-alpha; addresses the other half of bug 988.
1931 - Make the bridge directory authority refuse to answer directory
1932 requests for "all descriptors". It used to include bridge
1933 descriptors in its answer, which was a major information leak.
1934 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
1936 o Privacy fixes (clients):
1937 - When receiving a hidden service descriptor, check that it is for
1938 the hidden service we wanted. Previously, Tor would store any
1939 hidden service descriptors that a directory gave it, whether it
1940 wanted them or not. This wouldn't have let an attacker impersonate
1941 a hidden service, but it did let directories pre-seed a client
1942 with descriptors that it didn't want. Bugfix on 0.0.6.
1943 - Start the process of disabling ".exit" address notation, since it
1944 can be used for a variety of esoteric application-level attacks
1945 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
1947 - Reject attempts at the client side to open connections to private
1948 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
1949 a randomly chosen exit node. Attempts to do so are always
1950 ill-defined, generally prevented by exit policies, and usually
1951 in error. This will also help to detect loops in transparent
1952 proxy configurations. You can disable this feature by setting
1953 "ClientRejectInternalAddresses 0" in your torrc.
1954 - Log a notice when we get a new control connection. Now it's easier
1955 for security-conscious users to recognize when a local application
1956 is knocking on their controller door. Suggested by bug 1196.
1958 o Privacy fixes (newnym):
1959 - Avoid linkability based on cached hidden service descriptors: forget
1960 all hidden service descriptors cached as a client when processing a
1961 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
1962 - On SIGHUP, do not clear out all TrackHostExits mappings, client
1963 DNS cache entries, and virtual address mappings: that's what
1964 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
1965 - Don't attach new streams to old rendezvous circuits after SIGNAL
1966 NEWNYM. Previously, we would keep using an existing rendezvous
1967 circuit if it remained open (i.e. if it were kept open by a
1968 long-lived stream, or if a new stream were attached to it before
1969 Tor could notice that it was old and no longer in use). Bugfix on
1970 0.1.1.15-rc; fixes bug 3375.
1972 o Major bugfixes (relay bandwidth accounting):
1973 - Fix a bug that could break accounting on 64-bit systems with large
1974 time_t values, making them hibernate for impossibly long intervals.
1975 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
1976 - Fix a bug in bandwidth accounting that could make us use twice
1977 the intended bandwidth when our interval start changes due to
1978 daylight saving time. Now we tolerate skew in stored vs computed
1979 interval starts: if the start of the period changes by no more than
1980 50% of the period's duration, we remember bytes that we transferred
1981 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
1983 o Major bugfixes (bridges):
1984 - Bridges now use "reject *:*" as their default exit policy. Bugfix
1985 on 0.2.0.3-alpha. Fixes bug 1113.
1986 - If you configure your bridge with a known identity fingerprint,
1987 and the bridge authority is unreachable (as it is in at least
1988 one country now), fall back to directly requesting the descriptor
1989 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
1991 - Fix a bug where bridge users who configure the non-canonical
1992 address of a bridge automatically switch to its canonical
1993 address. If a bridge listens at more than one address, it
1994 should be able to advertise those addresses independently and
1995 any non-blocked addresses should continue to work. Bugfix on Tor
1996 0.2.0.3-alpha. Fixes bug 2510.
1997 - If you configure Tor to use bridge A, and then quit and
1998 configure Tor to use bridge B instead (or if you change Tor
1999 to use bridge B via the controller), it would happily continue
2000 to use bridge A if it's still reachable. While this behavior is
2001 a feature if your goal is connectivity, in some scenarios it's a
2002 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
2003 - When the controller configures a new bridge, don't wait 10 to 60
2004 seconds before trying to fetch its descriptor. Bugfix on
2005 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
2007 o Major bugfixes (directory authorities):
2008 - Many relays have been falling out of the consensus lately because
2009 not enough authorities know about their descriptor for them to get
2010 a majority of votes. When we deprecated the v2 directory protocol,
2011 we got rid of the only way that v3 authorities can hear from each
2012 other about other descriptors. Now authorities examine every v3
2013 vote for new descriptors, and fetch them from that authority. Bugfix
2015 - Authorities could be tricked into giving out the Exit flag to relays
2016 that didn't allow exiting to any ports. This bug could screw
2017 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
2018 1238. Bug discovered by Martin Kowalczyk.
2019 - If all authorities restart at once right before a consensus vote,
2020 nobody will vote about "Running", and clients will get a consensus
2021 with no usable relays. Instead, authorities refuse to build a
2022 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
2024 o Major bugfixes (stream-level fairness):
2025 - When receiving a circuit-level SENDME for a blocked circuit, try
2026 to package cells fairly from all the streams that had previously
2027 been blocked on that circuit. Previously, we had started with the
2028 oldest stream, and allowed each stream to potentially exhaust
2029 the circuit's package window. This gave older streams on any
2030 given circuit priority over newer ones. Fixes bug 1937. Detected
2031 originally by Camilo Viecco. This bug was introduced before the
2032 first Tor release, in svn commit r152: it is the new winner of
2033 the longest-lived bug prize.
2034 - Fix a stream fairness bug that would cause newer streams on a given
2035 circuit to get preference when reading bytes from the origin or
2036 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
2037 introduced before the first Tor release, in svn revision r152.
2038 - When the exit relay got a circuit-level sendme cell, it started
2039 reading on the exit streams, even if had 500 cells queued in the
2040 circuit queue already, so the circuit queue just grew and grew in
2041 some cases. We fix this by not re-enabling reading on receipt of a
2042 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
2043 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
2045 - Newly created streams were allowed to read cells onto circuits,
2046 even if the circuit's cell queue was blocked and waiting to drain.
2047 This created potential unfairness, as older streams would be
2048 blocked, but newer streams would gladly fill the queue completely.
2049 We add code to detect this situation and prevent any stream from
2050 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
2053 o Major bugfixes (hidden services):
2054 - Apply circuit timeouts to opened hidden-service-related circuits
2055 based on the correct start time. Previously, we would apply the
2056 circuit build timeout based on time since the circuit's creation;
2057 it was supposed to be applied based on time since the circuit
2058 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
2059 - Improve hidden service robustness: When we find that we have
2060 extended a hidden service's introduction circuit to a relay not
2061 listed as an introduction point in the HS descriptor we currently
2062 have, retry with an introduction point from the current
2063 descriptor. Previously we would just give up. Fixes bugs 1024 and
2064 1930; bugfix on 0.2.0.10-alpha.
2065 - Directory authorities now use data collected from their own
2066 uptime observations when choosing whether to assign the HSDir flag
2067 to relays, instead of trusting the uptime value the relay reports in
2068 its descriptor. This change helps prevent an attack where a small
2069 set of nodes with frequently-changing identity keys can blackhole
2070 a hidden service. (Only authorities need upgrade; others will be
2071 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
2072 - Stop assigning the HSDir flag to relays that disable their
2073 DirPort (and thus will refuse to answer directory requests). This
2074 fix should dramatically improve the reachability of hidden services:
2075 hidden services and hidden service clients pick six HSDir relays
2076 to store and retrieve the hidden service descriptor, and currently
2077 about half of the HSDir relays will refuse to work. Bugfix on
2078 0.2.0.10-alpha; fixes part of bug 1693.
2080 o Major bugfixes (misc):
2081 - Clients now stop trying to use an exit node associated with a given
2082 destination by TrackHostExits if they fail to reach that exit node.
2083 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
2084 - Fix a regression that caused Tor to rebind its ports if it receives
2085 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
2086 - Remove an extra pair of quotation marks around the error
2087 message in control-port STATUS_GENERAL BUG events. Bugfix on
2088 0.1.2.6-alpha; fixes bug 3732.
2090 o Minor features (relays):
2091 - Ensure that no empty [dirreq-](read|write)-history lines are added
2092 to an extrainfo document. Implements ticket 2497.
2093 - When bandwidth accounting is enabled, be more generous with how
2094 much bandwidth we'll use up before entering "soft hibernation".
2095 Previously, we'd refuse new connections and circuits once we'd
2096 used up 95% of our allotment. Now, we use up 95% of our allotment,
2097 AND make sure that we have no more than 500MB (or 3 hours of
2098 expected traffic, whichever is lower) remaining before we enter
2100 - Relays now log the reason for publishing a new relay descriptor,
2101 so we have a better chance of hunting down instances of bug 1810.
2102 Resolves ticket 3252.
2103 - Log a little more clearly about the times at which we're no longer
2104 accepting new connections (e.g. due to hibernating). Resolves
2106 - When AllowSingleHopExits is set, print a warning to explain to the
2107 relay operator why most clients are avoiding her relay.
2108 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
2109 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
2110 clients are already deprecated because of security bugs.
2112 o Minor features (network statistics):
2113 - Directory mirrors that set "DirReqStatistics 1" write statistics
2114 about directory requests to disk every 24 hours. As compared to the
2115 "--enable-geoip-stats" ./configure flag in 0.2.1.x, there are a few
2116 improvements: 1) stats are written to disk exactly every 24 hours;
2117 2) estimated shares of v2 and v3 requests are determined as mean
2118 values, not at the end of a measurement period; 3) unresolved
2119 requests are listed with country code '??'; 4) directories also
2120 measure download times.
2121 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
2122 number of exit streams and transferred bytes per port to disk every
2124 - Relays that set "CellStatistics 1" write statistics on how long
2125 cells spend in their circuit queues to disk every 24 hours.
2126 - Entry nodes that set "EntryStatistics 1" write statistics on the
2127 rough number and origins of connecting clients to disk every 24
2129 - Relays that write any of the above statistics to disk and set
2130 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
2131 their extra-info documents. Implements proposal 166.
2133 o Minor features (GeoIP and statistics):
2134 - Provide a log message stating which geoip file we're parsing
2135 instead of just stating that we're parsing the geoip file.
2136 Implements ticket 2432.
2137 - Make sure every relay writes a state file at least every 12 hours.
2138 Previously, a relay could go for weeks without writing its state
2139 file, and on a crash could lose its bandwidth history, capacity
2140 estimates, client country statistics, and so on. Addresses bug 3012.
2141 - Relays report the number of bytes spent on answering directory
2142 requests in extra-info descriptors similar to {read,write}-history.
2143 Implements enhancement 1790.
2144 - Report only the top 10 ports in exit-port stats in order not to
2145 exceed the maximum extra-info descriptor length of 50 KB. Implements
2147 - If writing the state file to disk fails, wait up to an hour before
2148 retrying again, rather than trying again each second. Fixes bug
2149 2346; bugfix on Tor 0.1.1.3-alpha.
2150 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
2151 when we switch from being a public relay to a bridge. Otherwise
2152 there will still be clients that see the relay in their consensus,
2153 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes
2155 - Update to the August 2 2011 Maxmind GeoLite Country database.
2157 o Minor features (clients):
2158 - When expiring circuits, use microsecond timers rather than
2159 one-second timers. This can avoid an unpleasant situation where a
2160 circuit is launched near the end of one second and expired right
2161 near the beginning of the next, and prevent fluctuations in circuit
2163 - If we've configured EntryNodes and our network goes away and/or all
2164 our entrynodes get marked down, optimistically retry them all when
2165 a new socks application request appears. Fixes bug 1882.
2166 - Always perform router selections using weighted relay bandwidth,
2167 even if we don't need a high capacity circuit at the time. Non-fast
2168 circuits now only differ from fast ones in that they can use relays
2169 not marked with the Fast flag. This "feature" could turn out to
2170 be a horrible bug; we should investigate more before it goes into
2172 - When we run out of directory information such that we can't build
2173 circuits, but then get enough that we can build circuits, log when
2174 we actually construct a circuit, so the user has a better chance of
2175 knowing what's going on. Fixes bug 1362.
2176 - Log SSL state transitions at debug level during handshake, and
2177 include SSL states in error messages. This may help debug future
2178 SSL handshake issues.
2180 o Minor features (directory authorities):
2181 - When a router changes IP address or port, authorities now launch
2182 a new reachability test for it. Implements ticket 1899.
2183 - Directory authorities now reject relays running any versions of
2184 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
2185 known bugs that keep RELAY_EARLY cells from working on rendezvous
2186 circuits. Followup to fix for bug 2081.
2187 - Directory authorities now reject relays running any version of Tor
2188 older than 0.2.0.26-rc. That version is the earliest that fetches
2189 current directory information correctly. Fixes bug 2156.
2190 - Directory authorities now do an immediate reachability check as soon
2191 as they hear about a new relay. This change should slightly reduce
2192 the time between setting up a relay and getting listed as running
2193 in the consensus. It should also improve the time between setting
2194 up a bridge and seeing use by bridge users.
2195 - Directory authorities no longer launch a TLS connection to every
2196 relay as they startup. Now that we have 2k+ descriptors cached,
2197 the resulting network hiccup is becoming a burden. Besides,
2198 authorities already avoid voting about Running for the first half
2199 hour of their uptime.
2200 - Directory authorities now log the source of a rejected POSTed v3
2201 networkstatus vote, so we can track failures better.
2202 - Backport code from 0.2.3.x that allows directory authorities to
2203 clean their microdescriptor caches. Needed to resolve bug 2230.
2205 o Minor features (hidden services):
2206 - Use computed circuit-build timeouts to decide when to launch
2207 parallel introduction circuits for hidden services. (Previously,
2208 we would retry after 15 seconds.)
2209 - Don't allow v0 hidden service authorities to act as clients.
2210 Required by fix for bug 3000.
2211 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
2212 by fix for bug 3000.
2213 - Make hidden services work better in private Tor networks by not
2214 requiring any uptime to join the hidden service descriptor
2215 DHT. Implements ticket 2088.
2216 - Log (at info level) when purging pieces of hidden-service-client
2217 state because of SIGNAL NEWNYM.
2219 o Minor features (controller interface):
2220 - New "GETINFO net/listeners/(type)" controller command to return
2221 a list of addresses and ports that are bound for listeners for a
2222 given connection type. This is useful when the user has configured
2223 "SocksPort auto" and the controller needs to know which port got
2224 chosen. Resolves another part of ticket 3076.
2225 - Have the controller interface give a more useful message than
2226 "Internal Error" in response to failed GETINFO requests.
2227 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
2228 event, to give information on the current rate of circuit timeouts
2229 over our stored history.
2230 - The 'EXTENDCIRCUIT' control port command can now be used with
2231 a circ id of 0 and no path. This feature will cause Tor to build
2232 a new 'fast' general purpose circuit using its own path selection
2234 - Added a BUILDTIMEOUT_SET controller event to describe changes
2235 to the circuit build timeout.
2236 - New controller command "getinfo config-text". It returns the
2237 contents that Tor would write if you send it a SAVECONF command,
2238 so the controller can write the file to disk itself.
2240 o Minor features (controller protocol):
2241 - Add a new ControlSocketsGroupWritable configuration option: when
2242 it is turned on, ControlSockets are group-writeable by the default
2243 group of the current user. Patch by Jérémy Bobbio; implements
2245 - Tor now refuses to create a ControlSocket in a directory that is
2246 world-readable (or group-readable if ControlSocketsGroupWritable
2247 is 0). This is necessary because some operating systems do not
2248 enforce permissions on an AF_UNIX sockets. Permissions on the
2249 directory holding the socket, however, seems to work everywhere.
2250 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
2251 not. This would lead to a cookie that is still not group readable.
2252 Closes bug 1843. Suggested by katmagic.
2253 - Future-proof the controller protocol a bit by ignoring keyword
2254 arguments we do not recognize.
2256 o Minor features (more useful logging):
2257 - Revise most log messages that refer to nodes by nickname to
2258 instead use the "$key=nickname at address" format. This should be
2259 more useful, especially since nicknames are less and less likely
2260 to be unique. Resolves ticket 3045.
2261 - When an HTTPS proxy reports "403 Forbidden", we now explain
2262 what it means rather than calling it an unexpected status code.
2263 Closes bug 2503. Patch from Michael Yakubovich.
2264 - Rate-limit a warning about failures to download v2 networkstatus
2265 documents. Resolves part of bug 1352.
2266 - Rate-limit the "your application is giving Tor only an IP address"
2267 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
2268 - Rate-limit "Failed to hand off onionskin" warnings.
2269 - When logging a rate-limited warning, we now mention how many messages
2270 got suppressed since the last warning.
2271 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
2272 2 no signature, 4 required" messages about consensus signatures
2273 easier to read, and make sure they get logged at the same severity
2274 as the messages explaining which keys are which. Fixes bug 1290.
2275 - Don't warn when we have a consensus that we can't verify because
2276 of missing certificates, unless those certificates are ones
2277 that we have been trying and failing to download. Fixes bug 1145.
2279 o Minor features (log domains):
2280 - Add documentation for configuring logging at different severities in
2281 different log domains. We've had this feature since 0.2.1.1-alpha,
2282 but for some reason it never made it into the manpage. Fixes
2284 - Make it simpler to specify "All log domains except for A and B".
2285 Previously you needed to say "[*,~A,~B]". Now you can just say
2287 - Add a "LogMessageDomains 1" option to include the domains of log
2288 messages along with the messages. Without this, there's no way
2289 to use log domains without reading the source or doing a lot
2291 - Add a new "Handshake" log domain for activities that happen
2292 during the TLS handshake.
2294 o Minor features (build process):
2295 - Make compilation with clang possible when using
2296 "--enable-gcc-warnings" by removing two warning options that clang
2297 hasn't implemented yet and by fixing a few warnings. Resolves
2299 - Detect platforms that brokenly use a signed size_t, and refuse to
2300 build there. Found and analyzed by doorss and rransom.
2301 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
2303 - Add support for statically linking zlib by specifying
2304 "--enable-static-zlib", to go with our support for statically
2305 linking openssl and libevent. Resolves bug 1358.
2306 - Instead of adding the svn revision to the Tor version string, report
2307 the git commit (when we're building from a git checkout).
2308 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
2310 - New --digests command-line switch to output the digests of the
2311 source files Tor was built with.
2312 - Generate our manpage and HTML documentation using Asciidoc. This
2313 change should make it easier to maintain the documentation, and
2314 produce nicer HTML. The build process fails if asciidoc cannot
2315 be found and building with asciidoc isn't disabled (via the
2316 "--disable-asciidoc" argument to ./configure. Skipping the manpage
2317 speeds up the build considerably.
2319 o Minor features (options / torrc):
2320 - Warn when the same option is provided more than once in a torrc
2321 file, on the command line, or in a single SETCONF statement, and
2322 the option is one that only accepts a single line. Closes bug 1384.
2323 - Warn when the user configures two HiddenServiceDir lines that point
2324 to the same directory. Bugfix on 0.0.6 (the version introducing
2325 HiddenServiceDir); fixes bug 3289.
2326 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
2327 do individual connection-level rate limiting of clients. The torrc
2328 config options with the same names trump the consensus params, if
2329 both are present. Replaces the old "bwconnrate" and "bwconnburst"
2330 consensus params which were broken from 0.2.2.7-alpha through
2331 0.2.2.14-alpha. Closes bug 1947.
2332 - New config option "WarnUnsafeSocks 0" disables the warning that
2333 occurs whenever Tor receives a socks handshake using a version of
2334 the socks protocol that can only provide an IP address (rather
2335 than a hostname). Setups that do DNS locally over Tor are fine,
2336 and we shouldn't spam the logs in that case.
2337 - New config option "CircuitStreamTimeout" to override our internal
2338 timeout schedule for how many seconds until we detach a stream from
2339 a circuit and try a new circuit. If your network is particularly
2340 slow, you might want to set this to a number like 60.
2341 - New options for SafeLogging to allow scrubbing only log messages
2342 generated while acting as a relay. Specify "SafeLogging relay" if
2343 you want to ensure that only messages known to originate from
2344 client use of the Tor process will be logged unsafely.
2345 - Time and memory units in the configuration file can now be set to
2346 fractional units. For example, "2.5 GB" is now a valid value for
2348 - Support line continuations in the torrc config file. If a line
2349 ends with a single backslash character, the newline is ignored, and
2350 the configuration value is treated as continuing on the next line.
2353 o Minor features (unit tests):
2354 - Revise our unit tests to use the "tinytest" framework, so we
2355 can run tests in their own processes, have smarter setup/teardown
2356 code, and so on. The unit test code has moved to its own
2357 subdirectory, and has been split into multiple modules.
2358 - Add a unit test for cross-platform directory-listing code.
2359 - Add some forgotten return value checks during unit tests. Found
2361 - Use GetTempDir to find the proper temporary directory location on
2362 Windows when generating temporary files for the unit tests. Patch
2365 o Minor features (misc):
2366 - The "torify" script now uses torsocks where available.
2367 - Make Libevent log messages get delivered to controllers later,
2368 and not from inside the Libevent log handler. This prevents unsafe
2369 reentrant Libevent calls while still letting the log messages
2371 - Certain Tor clients (such as those behind check.torproject.org) may
2372 want to fetch the consensus in an extra early manner. To enable this
2373 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
2374 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
2375 as only certain clients who must have this information sooner should
2377 - Expand homedirs passed to tor-checkkey. This should silence a
2378 coverity complaint about passing a user-supplied string into
2379 open() without checking it.
2380 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
2381 used on bridges, and it makes bridge scanning somewhat easier.
2382 - Create the /var/run/tor directory on startup on OpenSUSE if it is
2383 not already created. Patch from Andreas Stieger. Fixes bug 2573.
2385 o Minor bugfixes (relays):
2386 - When a relay decides that its DNS is too broken for it to serve
2387 as an exit server, it advertised itself as a non-exit, but
2388 continued to act as an exit. This could create accidental
2389 partitioning opportunities for users. Instead, if a relay is
2390 going to advertise reject *:* as its exit policy, it should
2391 really act with exit policy "reject *:*". Fixes bug 2366.
2392 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
2393 - Publish a router descriptor even if generating an extra-info
2394 descriptor fails. Previously we would not publish a router
2395 descriptor without an extra-info descriptor; this can cause fast
2396 exit relays collecting exit-port statistics to drop from the
2397 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
2398 - When we're trying to guess whether we know our IP address as
2399 a relay, we would log various ways that we failed to guess
2400 our address, but never log that we ended up guessing it
2401 successfully. Now add a log line to help confused and anxious
2402 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
2403 - For bandwidth accounting, calculate our expected bandwidth rate
2404 based on the time during which we were active and not in
2405 soft-hibernation during the last interval. Previously, we were
2406 also considering the time spent in soft-hibernation. If this
2407 was a long time, we would wind up underestimating our bandwidth
2408 by a lot, and skewing our wakeup time towards the start of the
2409 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
2410 - Demote a confusing TLS warning that relay operators might get when
2411 someone tries to talk to their ORPort. It is not the operator's
2412 fault, nor can they do anything about it. Fixes bug 1364; bugfix
2414 - Change "Application request when we're believed to be offline."
2415 notice to "Application request when we haven't used client
2416 functionality lately.", to clarify that it's not an error. Bugfix
2417 on 0.0.9.3; fixes bug 1222.
2419 o Minor bugfixes (bridges):
2420 - When a client starts or stops using bridges, never use a circuit
2421 that was built before the configuration change. This behavior could
2422 put at risk a user who uses bridges to ensure that her traffic
2423 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
2425 - Do not reset the bridge descriptor download status every time we
2426 re-parse our configuration or get a configuration change. Fixes
2427 bug 3019; bugfix on 0.2.0.3-alpha.
2428 - Users couldn't configure a regular relay to be their bridge. It
2429 didn't work because when Tor fetched the bridge descriptor, it found
2430 that it already had it, and didn't realize that the purpose of the
2431 descriptor had changed. Now we replace routers with a purpose other
2432 than bridge with bridge descriptors when fetching them. Bugfix on
2433 0.1.1.9-alpha. Fixes bug 1776.
2434 - In the special case where you configure a public exit relay as your
2435 bridge, Tor would be willing to use that exit relay as the last
2436 hop in your circuit as well. Now we fail that circuit instead.
2437 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
2439 o Minor bugfixes (clients):
2440 - We now ask the other side of a stream (the client or the exit)
2441 for more data on that stream when the amount of queued data on
2442 that stream dips low enough. Previously, we wouldn't ask the
2443 other side for more data until either it sent us more data (which
2444 it wasn't supposed to do if it had exhausted its window!) or we
2445 had completely flushed all our queued data. This flow control fix
2446 should improve throughput. Fixes bug 2756; bugfix on the earliest
2447 released versions of Tor (svn commit r152).
2448 - When a client finds that an origin circuit has run out of 16-bit
2449 stream IDs, we now mark it as unusable for new streams. Previously,
2450 we would try to close the entire circuit. Bugfix on 0.0.6.
2451 - Make it explicit that we don't cannibalize one-hop circuits. This
2452 happens in the wild, but doesn't turn out to be a problem because
2453 we fortunately don't use those circuits. Many thanks to outofwords
2454 for the initial analysis and to swissknife who confirmed that
2455 two-hop circuits are actually created.
2456 - Resolve an edge case in path weighting that could make us misweight
2457 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
2458 - Make the DNSPort option work with libevent 2.x. Don't alter the
2459 behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
2461 o Minor bugfixes (directory authorities):
2462 - Make directory authorities more accurate at recording when
2463 relays that have failed several reachability tests became
2464 unreachable, so we can provide more accuracy at assigning Stable,
2465 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
2466 - Directory authorities are now more robust to hops back in time
2467 when calculating router stability. Previously, if a run of uptime
2468 or downtime appeared to be negative, the calculation could give
2469 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
2471 - Directory authorities will now attempt to download consensuses
2472 if their own efforts to make a live consensus have failed. This
2473 change means authorities that restart will fetch a valid
2474 consensus, and it means authorities that didn't agree with the
2475 current consensus will still fetch and serve it if it has enough
2476 signatures. Bugfix on 0.2.0.9-alpha; fixes bug 1300.
2477 - Never vote for a server as "Running" if we have a descriptor for
2478 it claiming to be hibernating, and that descriptor was published
2479 more recently than our last contact with the server. Bugfix on
2480 0.2.0.3-alpha; fixes bug 911.
2481 - Directory authorities no longer change their opinion of, or vote on,
2482 whether a router is Running, unless they have themselves been
2483 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
2486 o Minor bugfixes (hidden services):
2487 - Log malformed requests for rendezvous descriptors as protocol
2488 warnings, not warnings. Also, use a more informative log message
2489 in case someone sees it at log level warning without prior
2490 info-level messages. Fixes bug 2748; bugfix on 0.2.0.10-alpha.
2491 - Accept hidden service descriptors if we think we might be a hidden
2492 service directory, regardless of what our consensus says. This
2493 helps robustness, since clients and hidden services can sometimes
2494 have a more up-to-date view of the network consensus than we do,
2495 and if they think that the directory authorities list us a HSDir,
2496 we might actually be one. Related to bug 2732; bugfix on
2498 - Correct the warning displayed when a rendezvous descriptor exceeds
2499 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
2501 - Clients and hidden services now use HSDir-flagged relays for hidden
2502 service descriptor downloads and uploads even if the relays have no
2503 DirPort set and the client has disabled TunnelDirConns. This will
2504 eventually allow us to give the HSDir flag to relays with no
2505 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
2506 - Only limit the lengths of single HS descriptors, even when multiple
2507 HS descriptors are published to an HSDir relay in a single POST
2508 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
2510 o Minor bugfixes (controllers):
2511 - Allow GETINFO fingerprint to return a fingerprint even when
2512 we have not yet built a router descriptor. Fixes bug 3577;
2513 bugfix on 0.2.0.1-alpha.
2514 - Send a SUCCEEDED stream event to the controller when a reverse
2515 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
2516 discovered by katmagic.
2517 - Remove a trailing asterisk from "exit-policy/default" in the
2518 output of the control port command "GETINFO info/names". Bugfix
2520 - Make the SIGNAL DUMP controller command work on FreeBSD. Fixes bug
2521 2917. Bugfix on 0.1.1.1-alpha.
2522 - When we restart our relay, we might get a successful connection
2523 from the outside before we've started our reachability tests,
2524 triggering a warning: "ORPort found reachable, but I have no
2525 routerinfo yet. Failing to inform controller of success." This
2526 bug was harmless unless Tor is running under a controller
2527 like Vidalia, in which case the controller would never get a
2528 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
2530 - When a controller changes TrackHostExits, remove mappings for
2531 hosts that should no longer have their exits tracked. Bugfix on
2533 - When a controller changes VirtualAddrNetwork, remove any mappings
2534 for hosts that were automapped to the old network. Bugfix on
2536 - When a controller changes one of the AutomapHosts* options, remove
2537 any mappings for hosts that should no longer be automapped. Bugfix
2539 - Fix an off-by-one error in calculating some controller command
2540 argument lengths. Fortunately, this mistake is harmless since
2541 the controller code does redundant NUL termination too. Found by
2542 boboper. Bugfix on 0.1.1.1-alpha.
2543 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
2544 would return "551 Internal error" rather than "552 Unrecognized key
2545 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
2546 - Don't spam the controller with events when we have no file
2547 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
2548 for log messages was already solved from bug 748.)
2549 - Emit a GUARD DROPPED controller event for a case we missed.
2550 - Ensure DNS requests launched by "RESOLVE" commands from the
2551 controller respect the __LeaveStreamsUnattached setconf options. The
2552 same goes for requests launched via DNSPort or transparent
2553 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
2555 o Minor bugfixes (config options):
2556 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
2557 Change the limit to 512 characters by removing base64 newlines.
2558 Fixes bug 2752. Fix by Michael Yakubovich.
2559 - Complain if PublishServerDescriptor is given multiple arguments that
2560 include 0 or 1. This configuration will be rejected in the future.
2561 Bugfix on 0.2.0.1-alpha; closes bug 1107.
2562 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
2563 Bugfix on 0.2.0.13-alpha; closes bug 928.
2565 o Minor bugfixes (log subsystem fixes):
2566 - When unable to format an address as a string, report its value
2567 as "???" rather than reusing the last formatted address. Bugfix
2569 - Be more consistent in our treatment of file system paths. "~" should
2570 get expanded to the user's home directory in the Log config option.
2571 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
2572 feature for the -f and --DataDirectory options.
2574 o Minor bugfixes (memory management):
2575 - Don't stack-allocate the list of supplementary GIDs when we're
2576 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
2577 could take up to 256K, which is way too much stack. Found by
2578 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
2579 - Save a couple bytes in memory allocation every time we escape
2580 certain characters in a string. Patch from Florian Zumbiehl.
2582 o Minor bugfixes (protocol correctness):
2583 - When checking for 1024-bit keys, check for 1024 bits, not 128
2584 bytes. This allows Tor to correctly discard keys of length 1017
2585 through 1023. Bugfix on 0.0.9pre5.
2586 - Require that introduction point keys and onion handshake keys
2587 have a public exponent of 65537. Starts to fix bug 3207; bugfix
2589 - Handle SOCKS messages longer than 128 bytes long correctly, rather
2590 than waiting forever for them to finish. Fixes bug 2330; bugfix
2591 on 0.2.0.16-alpha. Found by doorss.
2592 - Never relay a cell for a circuit we have already destroyed.
2593 Between marking a circuit as closeable and finally closing it,
2594 it may have been possible for a few queued cells to get relayed,
2595 even though they would have been immediately dropped by the next
2596 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
2597 - Never queue a cell for a circuit that's already been marked
2599 - Fix a spec conformance issue: the network-status-version token
2600 must be the first token in a v3 consensus or vote. Discovered by
2601 "parakeep". Bugfix on 0.2.0.3-alpha.
2602 - A networkstatus vote must contain exactly one signature. Spec
2603 conformance issue. Bugfix on 0.2.0.3-alpha.
2604 - When asked about a DNS record type we don't support via a
2605 client DNSPort, reply with NOTIMPL rather than an empty
2606 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
2607 - Make more fields in the controller protocol case-insensitive, since
2608 control-spec.txt said they were.
2610 o Minor bugfixes (log messages):
2611 - Fix a log message that said "bits" while displaying a value in
2612 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
2614 - Downgrade "no current certificates known for authority" message from
2615 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
2616 - Correctly describe errors that occur when generating a TLS object.
2617 Previously we would attribute them to a failure while generating a
2618 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
2620 - Fix an instance where a Tor directory mirror might accidentally
2621 log the IP address of a misbehaving Tor client. Bugfix on
2623 - Stop logging at severity 'warn' when some other Tor client tries
2624 to establish a circuit with us using weak DH keys. It's a protocol
2625 violation, but that doesn't mean ordinary users need to hear about
2626 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
2627 - If your relay can't keep up with the number of incoming create
2628 cells, it would log one warning per failure into your logs. Limit
2629 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
2631 o Minor bugfixes (build fixes):
2632 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
2633 - When warning about missing zlib development packages during compile,
2634 give the correct package names. Bugfix on 0.2.0.1-alpha.
2635 - Fix warnings that newer versions of autoconf produce during
2636 ./autogen.sh. These warnings appear to be harmless in our case,
2637 but they were extremely verbose. Fixes bug 2020.
2638 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
2641 o Minor bugfixes (portability):
2642 - Write several files in text mode, on OSes that distinguish text
2643 mode from binary mode (namely, Windows). These files are:
2644 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
2645 that collect those statistics; 'client_keys' and 'hostname' for
2646 hidden services that use authentication; and (in the tor-gencert
2647 utility) newly generated identity and signing keys. Previously,
2648 we wouldn't specify text mode or binary mode, leading to an
2649 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
2650 the DirRecordUsageByCountry option which would have triggered
2651 the assertion failure was added), although this assertion failure
2652 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
2653 - Selectively disable deprecation warnings on OS X because Lion
2654 started deprecating the shipped copy of openssl. Fixes bug 3643.
2655 - Use a wide type to hold sockets when built for 64-bit Windows.
2657 - Fix an issue that prevented static linking of libevent on
2658 some platforms (notably Linux). Fixes bug 2698; bugfix on 0.2.1.23,
2659 where we introduced the "--with-static-libevent" configure option.
2660 - Fix a bug with our locking implementation on Windows that couldn't
2661 correctly detect when a file was already locked. Fixes bug 2504,
2662 bugfix on 0.2.1.6-alpha.
2663 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
2665 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
2666 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
2669 o Minor bugfixes (code correctness):
2670 - Always NUL-terminate the sun_path field of a sockaddr_un before
2671 passing it to the kernel. (Not a security issue: kernels are
2672 smart enough to reject bad sockaddr_uns.) Found by Coverity;
2673 CID #428. Bugfix on Tor 0.2.0.3-alpha.
2674 - Make connection_printf_to_buf()'s behaviour sane. Its callers
2675 expect it to emit a CRLF iff the format string ends with CRLF;
2676 it actually emitted a CRLF iff (a) the format string ended with
2677 CRLF or (b) the resulting string was over 1023 characters long or
2678 (c) the format string did not end with CRLF *and* the resulting
2679 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
2680 fixes part of bug 3407.
2681 - Make send_control_event_impl()'s behaviour sane. Its callers
2682 expect it to always emit a CRLF at the end of the string; it
2683 might have emitted extra control characters as well. Bugfix on
2684 0.1.1.9-alpha; fixes another part of bug 3407.
2685 - Make crypto_rand_int() check the value of its input correctly.
2686 Previously, it accepted values up to UINT_MAX, but could return a
2687 negative number if given a value above INT_MAX+1. Found by George
2688 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
2689 - Fix a potential null-pointer dereference while computing a
2690 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
2692 - If we fail to compute the identity digest of a v3 legacy keypair,
2693 warn, and don't use a buffer-full of junk instead. Bugfix on
2694 0.2.1.1-alpha; fixes bug 3106.
2695 - Resolve an untriggerable issue in smartlist_string_num_isin(),
2696 where if the function had ever in the future been used to check
2697 for the presence of a too-large number, it would have given an
2698 incorrect result. (Fortunately, we only used it for 16-bit
2699 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
2700 - Be more careful about reporting the correct error from a failed
2701 connect() system call. Under some circumstances, it was possible to
2702 look at an incorrect value for errno when sending the end reason.
2703 Bugfix on 0.1.0.1-rc.
2704 - Correctly handle an "impossible" overflow cases in connection byte
2705 counting, where we write or read more than 4GB on an edge connection
2706 in a single second. Bugfix on 0.1.2.8-beta.
2707 - Avoid a double mark-for-free warning when failing to attach a
2708 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
2710 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
2711 found by "cypherpunks". This bug was introduced before the first
2712 Tor release, in svn commit r110.
2713 - Fix a bug in bandwidth history state parsing that could have been
2714 triggered if a future version of Tor ever changed the timing
2715 granularity at which bandwidth history is measured. Bugfix on
2717 - Add assertions to check for overflow in arguments to
2718 base32_encode() and base32_decode(); fix a signed-unsigned
2719 comparison there too. These bugs are not actually reachable in Tor,
2720 but it's good to prevent future errors too. Found by doorss.
2721 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
2723 - Set target port in get_interface_address6() correctly. Bugfix
2724 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
2725 - Fix an impossible-to-actually-trigger buffer overflow in relay
2726 descriptor generation. Bugfix on 0.1.0.15.
2727 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
2729 o Minor bugfixes (code improvements):
2730 - After we free an internal connection structure, overwrite it
2731 with a different memory value than we use for overwriting a freed
2732 internal circuit structure. Should help with debugging. Suggested
2734 - If OpenSSL fails to make a duplicate of a private or public key, log
2735 an error message and try to exit cleanly. May help with debugging
2736 if bug 1209 ever remanifests.
2737 - Some options used different conventions for uppercasing of acronyms
2738 when comparing manpage and source. Fix those in favor of the
2739 manpage, as it makes sense to capitalize acronyms.
2740 - Take a first step towards making or.h smaller by splitting out
2741 function definitions for all source files in src/or/. Leave
2742 structures and defines in or.h for now.
2743 - Remove a few dead assignments during router parsing. Found by
2745 - Don't use 1-bit wide signed bit fields. Found by coverity.
2746 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
2747 None of the cases where we did this before were wrong, but by making
2748 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
2749 - The memarea code now uses a sentinel value at the end of each area
2750 to make sure nothing writes beyond the end of an area. This might
2751 help debug some conceivable causes of bug 930.
2752 - Always treat failure to allocate an RSA key as an unrecoverable
2754 - Add some more defensive programming for architectures that can't
2755 handle unaligned integer accesses. We don't know of any actual bugs
2756 right now, but that's the best time to fix them. Fixes bug 1943.
2758 o Minor bugfixes (misc):
2759 - Fix a rare bug in rend_fn unit tests: we would fail a test when
2760 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
2761 on 0.2.0.10-alpha; fixes bug 1808.
2762 - Where available, use Libevent 2.0's periodic timers so that our
2763 once-per-second cleanup code gets called even more closely to
2764 once per second than it would otherwise. Fixes bug 943.
2765 - Ignore OutboundBindAddress when connecting to localhost.
2766 Connections to localhost need to come _from_ localhost, or else
2767 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
2769 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
2771 - If any of the v3 certs we download are unparseable, we should
2772 actually notice the failure so we don't retry indefinitely. Bugfix
2773 on 0.2.0.x; reported by "rotator".
2774 - When Tor fails to parse a descriptor of any kind, dump it to disk.
2775 Might help diagnosing bug 1051.
2776 - Make our 'torify' script more portable; if we have only one of
2777 'torsocks' or 'tsocks' installed, don't complain to the user;
2778 and explain our warning about tsocks better.
2779 - Fix some urls in the exit notice file and make it XHTML1.1 strict
2780 compliant. Based on a patch from Christian Kujau.
2782 o Documentation changes:
2783 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
2784 - Resolve all doxygen warnings except those for missing documentation.
2786 - Add doxygen documentation for more functions, fields, and types.
2787 - Convert the HACKING file to asciidoc, and add a few new sections
2788 to it, explaining how we use Git, how we make changelogs, and
2789 what should go in a patch.
2790 - Document the default socks host and port (127.0.0.1:9050) for
2792 - Removed some unnecessary files from the source distribution. The
2793 AUTHORS file has now been merged into the people page on the
2794 website. The roadmaps and design doc can now be found in the
2795 projects directory in svn.
2797 o Deprecated and removed features (config):
2798 - Remove the torrc.complete file. It hasn't been kept up to date
2799 and users will have better luck checking out the manpage.
2800 - Remove the HSAuthorityRecordStats option that version 0 hidden
2801 service authorities could use to track statistics of overall v0
2802 hidden service usage.
2803 - Remove the obsolete "NoPublish" option; it has been flagged
2804 as obsolete and has produced a warning since 0.1.1.18-rc.
2805 - Caches no longer download and serve v2 networkstatus documents
2806 unless FetchV2Networkstatus flag is set: these documents haven't
2807 haven't been used by clients or relays since 0.2.0.x. Resolves
2810 o Deprecated and removed features (controller):
2811 - The controller no longer accepts the old obsolete "addr-mappings/"
2812 or "unregistered-servers-" GETINFO values.
2813 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
2814 always on; using them is necessary for correct forward-compatible
2817 o Deprecated and removed features (misc):
2818 - Hidden services no longer publish version 0 descriptors, and clients
2819 do not request or use version 0 descriptors. However, the old hidden
2820 service authorities still accept and serve version 0 descriptors
2821 when contacted by older hidden services/clients.
2822 - Remove undocumented option "-F" from tor-resolve: it hasn't done
2823 anything since 0.2.1.16-rc.
2824 - Remove everything related to building the expert bundle for OS X.
2825 It has confused many users, doesn't work right on OS X 10.6,
2826 and is hard to get rid of once installed. Resolves bug 1274.
2827 - Remove support for .noconnect style addresses. Nobody was using
2828 them, and they provided another avenue for detecting Tor users
2829 via application-level web tricks.
2830 - When we fixed bug 1038 we had to put in a restriction not to send
2831 RELAY_EARLY cells on rend circuits. This was necessary as long
2832 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
2833 active. Now remove this obsolete check. Resolves bug 2081.
2834 - Remove workaround code to handle directory responses from servers
2835 that had bug 539 (they would send HTTP status 503 responses _and_
2836 send a body too). Since only server versions before
2837 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
2838 keep the workaround in place.
2839 - Remove the old 'fuzzy time' logic. It was supposed to be used for
2840 handling calculations where we have a known amount of clock skew and
2841 an allowed amount of unknown skew. But we only used it in three
2842 places, and we never adjusted the known/unknown skew values. This is
2843 still something we might want to do someday, but if we do, we'll
2844 want to do it differently.
2845 - Remove the "--enable-iphone" option to ./configure. According to
2846 reports from Marco Bonetti, Tor builds fine without any special
2847 tweaking on recent iPhone SDK versions.
2850 Changes in version 0.2.1.30 - 2011-02-23
2851 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
2852 change is a slight tweak to Tor's TLS handshake that makes relays
2853 and bridges that run this new version reachable from Iran again.
2854 We don't expect this tweak will win the arms race long-term, but it
2855 buys us time until we roll out a better solution.
2858 - Stop sending a CLOCK_SKEW controller status event whenever
2859 we fetch directory information from a relay that has a wrong clock.
2860 Instead, only inform the controller when it's a trusted authority
2861 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
2862 the rest of bug 1074.
2863 - Fix a bounds-checking error that could allow an attacker to
2864 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
2866 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
2867 Tor would ignore their RelayBandwidthBurst setting,
2868 potentially using more bandwidth than expected. Bugfix on
2869 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
2870 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
2871 hidserv" in her torrc. The 'hidserv' argument never controlled
2872 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
2875 - Adjust our TLS Diffie-Hellman parameters to match those used by
2877 - Update to the February 1 2011 Maxmind GeoLite Country database.
2880 - Check for and reject overly long directory certificates and
2881 directory tokens before they have a chance to hit any assertions.
2882 Bugfix on 0.2.1.28. Found by "doorss".
2883 - Bring the logic that gathers routerinfos and assesses the
2884 acceptability of circuits into line. This prevents a Tor OP from
2885 getting locked in a cycle of choosing its local OR as an exit for a
2886 path (due to a .exit request) and then rejecting the circuit because
2887 its OR is not listed yet. It also prevents Tor clients from using an
2888 OR running in the same instance as an exit (due to a .exit request)
2889 if the OR does not meet the same requirements expected of an OR
2890 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
2892 o Packaging changes:
2893 - Stop shipping the Tor specs files and development proposal documents
2894 in the tarball. They are now in a separate git repository at
2895 git://git.torproject.org/torspec.git
2896 - Do not include Git version tags as though they are SVN tags when
2897 generating a tarball from inside a repository that has switched
2898 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
2901 Changes in version 0.2.1.29 - 2011-01-15
2902 Tor 0.2.1.29 continues our recent code security audit work. The main
2903 fix resolves a remote heap overflow vulnerability that can allow remote
2904 code execution. Other fixes address a variety of assert and crash bugs,
2905 most of which we think are hard to exploit remotely.
2907 o Major bugfixes (security):
2908 - Fix a heap overflow bug where an adversary could cause heap
2909 corruption. This bug probably allows remote code execution
2910 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
2912 - Prevent a denial-of-service attack by disallowing any
2913 zlib-compressed data whose compression factor is implausibly
2914 high. Fixes part of bug 2324; reported by "doorss".
2915 - Zero out a few more keys in memory before freeing them. Fixes
2916 bug 2384 and part of bug 2385. These key instances found by
2917 "cypherpunks", based on Andrew Case's report about being able
2918 to find sensitive data in Tor's memory space if you have enough
2919 permissions. Bugfix on 0.0.2pre9.
2921 o Major bugfixes (crashes):
2922 - Prevent calls to Libevent from inside Libevent log handlers.
2923 This had potential to cause a nasty set of crashes, especially
2924 if running Libevent with debug logging enabled, and running
2925 Tor with a controller watching for low-severity log messages.
2926 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
2927 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
2928 underflow errors there too. Fixes the other part of bug 2324.
2929 - Fix a bug where we would assert if we ever had a
2930 cached-descriptors.new file (or another file read directly into
2931 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
2932 on 0.2.1.25. Found by doorss.
2933 - Fix some potential asserts and parsing issues with grossly
2934 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
2937 o Minor bugfixes (other):
2938 - Fix a bug with handling misformed replies to reverse DNS lookup
2939 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
2940 bug reported by doorss.
2941 - Fix compilation on mingw when a pthreads compatibility library
2942 has been installed. (We don't want to use it, so we shouldn't
2943 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
2944 - Fix a bug where we would declare that we had run out of virtual
2945 addresses when the address space was only half-exhausted. Bugfix
2947 - Correctly handle the case where AutomapHostsOnResolve is set but
2948 no virtual addresses are available. Fixes bug 2328; bugfix on
2949 0.1.2.1-alpha. Bug found by doorss.
2950 - Correctly handle wrapping around when we run out of virtual
2951 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
2954 - Update to the January 1 2011 Maxmind GeoLite Country database.
2955 - Introduce output size checks on all of our decryption functions.
2958 - Tor does not build packages correctly with Automake 1.6 and earlier;
2959 added a check to Makefile.am to make sure that we're building with
2960 Automake 1.7 or later.
2961 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
2962 because we built it with a too-old version of automake. Thus that
2963 release broke ./configure --enable-openbsd-malloc, which is popular
2964 among really fast exit relays on Linux.
2967 Changes in version 0.2.1.28 - 2010-12-17
2968 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
2969 exploitable bugs. We also took this opportunity to change the IP address
2970 for one of our directory authorities, and to update the geoip database
2974 - Fix a remotely exploitable bug that could be used to crash instances
2975 of Tor remotely by overflowing on the heap. Remote-code execution
2976 hasn't been confirmed, but can't be ruled out. Everyone should
2977 upgrade. Bugfix on the 0.1.1 series and later.
2979 o Directory authority changes:
2980 - Change IP address and ports for gabelmoo (v3 directory authority).
2983 - Update to the December 1 2010 Maxmind GeoLite Country database.
2986 Changes in version 0.2.1.27 - 2010-11-23
2987 Yet another OpenSSL security patch broke its compatibility with Tor:
2988 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
2989 also took this opportunity to fix several crash bugs, integrate a new
2990 directory authority, and update the bundled GeoIP database.
2993 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
2994 No longer set the tlsext_host_name extension on server SSL objects;
2995 but continue to set it on client SSL objects. Our goal in setting
2996 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
2997 bugfix on 0.2.1.1-alpha.
2998 - Do not log messages to the controller while shrinking buffer
2999 freelists. Doing so would sometimes make the controller connection
3000 try to allocate a buffer chunk, which would mess up the internals
3001 of the freelist and cause an assertion failure. Fixes bug 1125;
3002 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
3003 - Learn our external IP address when we're a relay or bridge, even if
3004 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
3005 where we introduced bridge relays that don't need to publish to
3006 be useful. Fixes bug 2050.
3007 - Do even more to reject (and not just ignore) annotations on
3008 router descriptors received anywhere but from the cache. Previously
3009 we would ignore such annotations at first, but cache them to disk
3010 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
3011 - When you're using bridges and your network goes away and your
3012 bridges get marked as down, recover when you attempt a new socks
3013 connection (if the network is back), rather than waiting up to an
3014 hour to try fetching new descriptors for your bridges. Bugfix on
3015 0.2.0.3-alpha; fixes bug 1981.
3018 - Move to the November 2010 Maxmind GeoLite country db (rather
3019 than the June 2009 ip-to-country GeoIP db) for our statistics that
3020 count how many users relays are seeing from each country. Now we'll
3021 have more accurate data, especially for many African countries.
3023 o New directory authorities:
3024 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
3028 - Fix an assertion failure that could occur in directory caches or
3029 bridge users when using a very short voting interval on a testing
3030 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
3032 - Enforce multiplicity rules when parsing annotations. Bugfix on
3033 0.2.0.8-alpha. Found by piebeer.
3034 - Allow handshaking OR connections to take a full KeepalivePeriod
3035 seconds to handshake. Previously, we would close them after
3036 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
3037 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
3039 - When building with --enable-gcc-warnings on OpenBSD, disable
3040 warnings in system headers. This makes --enable-gcc-warnings
3041 pass on OpenBSD 4.8.
3044 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
3045 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
3046 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
3047 Servers can start sending this code when enough clients recognize
3048 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
3049 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
3050 Patch from mingw-san.
3053 - Remove the old debian/ directory from the main Tor distribution.
3054 The official Tor-for-debian git repository lives at the URL
3055 https://git.torproject.org/debian/tor.git
3056 - Stop shipping the old doc/website/ directory in the tarball. We
3057 changed the website format in late 2010, and what we shipped in
3058 0.2.1.26 really wasn't that useful anyway.
3061 Changes in version 0.2.1.26 - 2010-05-02
3062 Tor 0.2.1.26 addresses the recent connection and memory overload
3063 problems we've been seeing on relays, especially relays with their
3064 DirPort open. If your relay has been crashing, or you turned it off
3065 because it used too many resources, give this release a try.
3067 This release also fixes yet another instance of broken OpenSSL libraries
3068 that was causing some relays to drop out of the consensus.
3071 - Teach relays to defend themselves from connection overload. Relays
3072 now close idle circuits early if it looks like they were intended
3073 for directory fetches. Relays are also more aggressive about closing
3074 TLS connections that have no circuits on them. Such circuits are
3075 unlikely to be re-used, and tens of thousands of them were piling
3076 up at the fast relays, causing the relays to run out of sockets
3077 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
3078 their directory fetches over TLS).
3079 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
3080 that claim to be earlier than 0.9.8m, but which have in reality
3081 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
3082 behavior. Possible fix for some cases of bug 1346.
3083 - Directory mirrors were fetching relay descriptors only from v2
3084 directory authorities, rather than v3 authorities like they should.
3085 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
3086 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
3089 - Finally get rid of the deprecated and now harmful notion of "clique
3090 mode", where directory authorities maintain TLS connections to
3094 - In the util/threads test, no longer free the test_mutex before all
3095 worker threads have finished. Bugfix on 0.2.1.6-alpha.
3096 - The master thread could starve the worker threads quite badly on
3097 certain systems, causing them to run only partially in the allowed
3098 window. This resulted in test failures. Now the master thread sleeps
3099 occasionally for a few microseconds while the two worker-threads
3100 compete for the mutex. Bugfix on 0.2.0.1-alpha.
3103 Changes in version 0.2.1.25 - 2010-03-16
3104 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
3105 prevent relays from guessing their IP address correctly. It also fixes
3106 several minor potential security bugs.
3109 - Fix a regression from our patch for bug 1244 that caused relays
3110 to guess their IP address incorrectly if they didn't set Address
3111 in their torrc and/or their address fails to resolve. Bugfix on
3112 0.2.1.23; fixes bug 1269.
3113 - When freeing a session key, zero it out completely. We only zeroed
3114 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
3115 patched by ekir. Fixes bug 1254.
3118 - Fix a dereference-then-NULL-check sequence when publishing
3119 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
3121 - Fix another dereference-then-NULL-check sequence. Bugfix on
3122 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
3123 - Make sure we treat potentially not NUL-terminated strings correctly.
3124 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
3127 Changes in version 0.2.1.24 - 2010-02-21
3128 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
3132 - Work correctly out-of-the-box with even more vendor-patched versions
3133 of OpenSSL. In particular, make it so Debian and OS X don't need
3134 customized patches to run/build.
3137 Changes in version 0.2.1.23 - 2010-02-13
3138 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
3139 again on the latest OS X, and updates the location of a directory
3142 o Major bugfixes (performance):
3143 - We were selecting our guards uniformly at random, and then weighting
3144 which of our guards we'd use uniformly at random. This imbalance
3145 meant that Tor clients were severely limited on throughput (and
3146 probably latency too) by the first hop in their circuit. Now we
3147 select guards weighted by currently advertised bandwidth. We also
3148 automatically discard guards picked using the old algorithm. Fixes
3149 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
3152 - Make Tor work again on the latest OS X: when deciding whether to
3153 use strange flags to turn TLS renegotiation on, detect the OpenSSL
3154 version at run-time, not compile time. We need to do this because
3155 Apple doesn't update its dev-tools headers when it updates its
3156 libraries in a security patch.
3157 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
3158 that could happen on 32-bit platforms with 64-bit time_t. Also fix
3159 a memory leak when requesting a hidden service descriptor we've
3160 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
3164 - Refactor resolve_my_address() to not use gethostbyname() anymore.
3165 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
3168 - Avoid a mad rush at the beginning of each month when each client
3169 rotates half of its guards. Instead we spread the rotation out
3170 throughout the month, but we still avoid leaving a precise timestamp
3171 in the state file about when we first picked the guard. Improves
3172 over the behavior introduced in 0.1.2.17.
3175 Changes in version 0.2.1.22 - 2010-01-19
3176 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
3177 authorities -- it would tell you its whole history of bridge descriptors
3178 if you make the right directory request. This stable update also
3179 rotates two of the seven v3 directory authority keys and locations.
3181 o Directory authority changes:
3182 - Rotate keys (both v3 identity and relay identity) for moria1
3186 - Stop bridge directory authorities from answering dbg-stability.txt
3187 directory queries, which would let people fetch a list of all
3188 bridge identities they track. Bugfix on 0.2.1.6-alpha.
3191 Changes in version 0.2.1.21 - 2009-12-21
3192 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
3193 library. If you use Tor on Linux / Unix and you're getting SSL
3194 renegotiation errors, upgrading should help. We also recommend an
3195 upgrade if you're an exit relay.
3198 - Work around a security feature in OpenSSL 0.9.8l that prevents our
3199 handshake from working unless we explicitly tell OpenSSL that we
3200 are using SSL renegotiation safely. We are, of course, but OpenSSL
3201 0.9.8l won't work unless we say we are.
3202 - Avoid crashing if the client is trying to upload many bytes and the
3203 circuit gets torn down at the same time, or if the flip side
3204 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
3207 - Do not refuse to learn about authority certs and v2 networkstatus
3208 documents that are older than the latest consensus. This bug might
3209 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
3210 Spotted and fixed by xmux.
3211 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
3212 trigger platform-specific option misparsing case found by Coverity
3214 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
3215 trigger assert. Fixes bug 1173.
3218 Changes in version 0.2.1.20 - 2009-10-15
3219 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
3220 services at once, prepares for more performance improvements, and
3221 fixes a bunch of smaller bugs.
3223 The Windows and OS X bundles also include a more recent Vidalia,
3224 and switch from Privoxy to Polipo.
3226 The OS X installers are now drag and drop. It's best to un-install
3227 Tor/Vidalia and then install this new bundle, rather than upgrade. If
3228 you want to upgrade, you'll need to update the paths for Tor and Polipo
3229 in the Vidalia Settings window.
3232 - Send circuit or stream sendme cells when our window has decreased
3233 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
3234 by Karsten when testing the "reduce circuit window" performance
3235 patch. Bugfix on the 54th commit on Tor -- from July 2002,
3236 before the release of Tor 0.0.0. This is the new winner of the
3238 - Fix a remotely triggerable memory leak when a consensus document
3239 contains more than one signature from the same voter. Bugfix on
3241 - Avoid segfault in rare cases when finishing an introduction circuit
3242 as a client and finding out that we don't have an introduction key
3243 for it. Fixes bug 1073. Reported by Aaron Swartz.
3246 - Tor now reads the "circwindow" parameter out of the consensus,
3247 and uses that value for its circuit package window rather than the
3248 default of 1000 cells. Begins the implementation of proposal 168.
3250 o New directory authorities:
3251 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
3253 - Move moria1 and tonga to alternate IP addresses.
3256 - Fix a signed/unsigned compile warning in 0.2.1.19.
3257 - Fix possible segmentation fault on directory authorities. Bugfix on
3259 - Fix an extremely rare infinite recursion bug that could occur if
3260 we tried to log a message after shutting down the log subsystem.
3261 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
3262 - Fix an obscure bug where hidden services on 64-bit big-endian
3263 systems might mis-read the timestamp in v3 introduce cells, and
3264 refuse to connect back to the client. Discovered by "rotor".
3265 Bugfix on 0.2.1.6-alpha.
3266 - We were triggering a CLOCK_SKEW controller status event whenever
3267 we connect via the v2 connection protocol to any relay that has
3268 a wrong clock. Instead, we should only inform the controller when
3269 it's a trusted authority that claims our clock is wrong. Bugfix
3270 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
3271 - We were telling the controller about CHECKING_REACHABILITY and
3272 REACHABILITY_FAILED status events whenever we launch a testing
3273 circuit or notice that one has failed. Instead, only tell the
3274 controller when we want to inform the user of overall success or
3275 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
3277 - Don't warn when we're using a circuit that ends with a node
3278 excluded in ExcludeExitNodes, but the circuit is not used to access
3279 the outside world. This should help fix bug 1090. Bugfix on
3281 - Work around a small memory leak in some versions of OpenSSL that
3282 stopped the memory used by the hostname TLS extension from being
3286 - Add a "getinfo status/accepted-server-descriptor" controller
3287 command, which is the recommended way for controllers to learn
3288 whether our server descriptor has been successfully received by at
3289 least on directory authority. Un-recommend good-server-descriptor
3290 getinfo and status events until we have a better design for them.
3293 Changes in version 0.2.1.19 - 2009-07-28
3294 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
3298 - Make accessing hidden services on 0.2.1.x work right again.
3299 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
3300 part of patch provided by "optimist".
3303 - When a relay/bridge is writing out its identity key fingerprint to
3304 the "fingerprint" file and to its logs, write it without spaces. Now
3305 it will look like the fingerprints in our bridges documentation,
3306 and confuse fewer users.
3309 - Relays no longer publish a new server descriptor if they change
3310 their MaxAdvertisedBandwidth config option but it doesn't end up
3311 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
3312 fixes bug 1026. Patch from Sebastian.
3313 - Avoid leaking memory every time we get a create cell but we have
3314 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
3315 fixes bug 1034. Reported by BarkerJr.
3318 Changes in version 0.2.1.18 - 2009-07-24
3319 Tor 0.2.1.18 lays the foundations for performance improvements,
3320 adds status events to help users diagnose bootstrap problems, adds
3321 optional authentication/authorization for hidden services, fixes a
3322 variety of potential anonymity problems, and includes a huge pile of
3323 other features and bug fixes.
3325 o Major features (clients):
3326 - Start sending "bootstrap phase" status events to the controller,
3327 so it can keep the user informed of progress fetching directory
3328 information and establishing circuits. Also inform the controller
3329 if we think we're stuck at a particular bootstrap phase. Implements
3331 - Clients replace entry guards that were chosen more than a few months
3332 ago. This change should significantly improve client performance,
3333 especially once more people upgrade, since relays that have been
3334 a guard for a long time are currently overloaded.
3335 - Network status consensus documents and votes now contain bandwidth
3336 information for each relay. Clients use the bandwidth values
3337 in the consensus, rather than the bandwidth values in each
3338 relay descriptor. This approach opens the door to more accurate
3339 bandwidth estimates once the directory authorities start doing
3340 active measurements. Implements part of proposal 141.
3342 o Major features (relays):
3343 - Disable and refactor some debugging checks that forced a linear scan
3344 over the whole server-side DNS cache. These accounted for over 50%
3345 of CPU time on a relatively busy exit node's gprof profile. Also,
3346 disable some debugging checks that appeared in exit node profile
3347 data. Found by Jacob.
3348 - New DirPortFrontPage option that takes an html file and publishes
3349 it as "/" on the DirPort. Now relay operators can provide a
3350 disclaimer without needing to set up a separate webserver. There's
3351 a sample disclaimer in contrib/tor-exit-notice.html.
3353 o Major features (hidden services):
3354 - Make it possible to build hidden services that only certain clients
3355 are allowed to connect to. This is enforced at several points,
3356 so that unauthorized clients are unable to send INTRODUCE cells
3357 to the service, or even (depending on the type of authentication)
3358 to learn introduction points. This feature raises the bar for
3359 certain kinds of active attacks against hidden services. Design
3360 and code by Karsten Loesing. Implements proposal 121.
3361 - Relays now store and serve v2 hidden service descriptors by default,
3362 i.e., the new default value for HidServDirectoryV2 is 1. This is
3363 the last step in proposal 114, which aims to make hidden service
3364 lookups more reliable.
3366 o Major features (path selection):
3367 - ExitNodes and Exclude*Nodes config options now allow you to restrict
3368 by country code ("{US}") or IP address or address pattern
3369 ("255.128.0.0/16"). Patch from Robert Hogan. It still needs some
3370 refinement to decide what config options should take priority if
3371 you ask to both use a particular node and exclude it.
3373 o Major features (misc):
3374 - When building a consensus, do not include routers that are down.
3375 This cuts down 30% to 40% on consensus size. Implements proposal
3377 - New TestingTorNetwork config option to allow adjustment of
3378 previously constant values that could slow bootstrapping. Implements
3379 proposal 135. Patch from Karsten.
3380 - Convert many internal address representations to optionally hold
3381 IPv6 addresses. Generate and accept IPv6 addresses in many protocol
3382 elements. Make resolver code handle nameservers located at IPv6
3384 - More work on making our TLS handshake blend in: modify the list
3385 of ciphers advertised by OpenSSL in client mode to even more
3386 closely resemble a common web browser. We cheat a little so that
3387 we can advertise ciphers that the locally installed OpenSSL doesn't
3389 - Use the TLS1 hostname extension to more closely resemble browser
3392 o Security fixes (anonymity/entropy):
3393 - Never use a connection with a mismatched address to extend a
3394 circuit, unless that connection is canonical. A canonical
3395 connection is one whose address is authenticated by the router's
3396 identity key, either in a NETINFO cell or in a router descriptor.
3397 - Implement most of proposal 110: The first K cells to be sent
3398 along a circuit are marked as special "early" cells; only K "early"
3399 cells will be allowed. Once this code is universal, we can block
3400 certain kinds of denial-of-service attack by requiring that EXTEND
3401 commands must be sent using an "early" cell.
3402 - Resume using OpenSSL's RAND_poll() for better (and more portable)
3403 cross-platform entropy collection again. We used to use it, then
3404 stopped using it because of a bug that could crash systems that
3405 called RAND_poll when they had a lot of fds open. It looks like the
3406 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
3407 at startup, and to call RAND_poll() when we reseed later only if
3408 we have a non-buggy OpenSSL version.
3409 - When the client is choosing entry guards, now it selects at most
3410 one guard from a given relay family. Otherwise we could end up with
3411 all of our entry points into the network run by the same operator.
3412 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
3413 - Do not use or believe expired v3 authority certificates. Patch
3414 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
3415 - Drop begin cells to a hidden service if they come from the middle
3416 of a circuit. Patch from lark.
3417 - When we erroneously receive two EXTEND cells for the same circuit
3418 ID on the same connection, drop the second. Patch from lark.
3419 - Authorities now vote for the Stable flag for any router whose
3420 weighted MTBF is at least 5 days, regardless of the mean MTBF.
3421 - Clients now never report any stream end reason except 'MISC'.
3422 Implements proposal 148.
3424 o Major bugfixes (crashes):
3425 - Parse dates and IPv4 addresses in a locale- and libc-independent
3426 manner, to avoid platform-dependent behavior on malformed input.
3427 - Fix a crash that occurs on exit nodes when a nameserver request
3428 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
3429 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
3431 - Do not assume that a stack-allocated character array will be
3432 64-bit aligned on platforms that demand that uint64_t access is
3433 aligned. Possible fix for bug 604.
3434 - Resolve a very rare crash bug that could occur when the user forced
3435 a nameserver reconfiguration during the middle of a nameserver
3436 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
3437 - Avoid a "0 divided by 0" calculation when calculating router uptime
3438 at directory authorities. Bugfix on 0.2.0.8-alpha.
3439 - Fix an assertion bug in parsing policy-related options; possible fix
3441 - Rate-limit too-many-sockets messages: when they happen, they happen
3442 a lot and end up filling up the disk. Resolves bug 748.
3443 - Fix a race condition that could cause crashes or memory corruption
3444 when running as a server with a controller listening for log
3446 - Avoid crashing when we have a policy specified in a DirPolicy or
3447 SocksPolicy or ReachableAddresses option with ports set on it,
3448 and we re-load the policy. May fix bug 996.
3449 - Fix an assertion failure on 64-bit platforms when we allocated
3450 memory right up to the end of a memarea, then realigned the memory
3451 one step beyond the end. Fixes a possible cause of bug 930.
3452 - Protect the count of open sockets with a mutex, so we can't
3453 corrupt it when two threads are closing or opening sockets at once.
3454 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
3456 o Major bugfixes (clients):
3457 - Discard router descriptors as we load them if they are more than
3458 five days old. Otherwise if Tor is off for a long time and then
3459 starts with cached descriptors, it will try to use the onion keys
3460 in those obsolete descriptors when building circuits. Fixes bug 887.
3461 - When we choose to abandon a new entry guard because we think our
3462 older ones might be better, close any circuits pending on that
3463 new entry guard connection. This fix should make us recover much
3464 faster when our network is down and then comes back. Bugfix on
3465 0.1.2.8-beta; found by lodger.
3466 - When Tor clients restart after 1-5 days, they discard all their
3467 cached descriptors as too old, but they still use the cached
3468 consensus document. This approach is good for robustness, but
3469 bad for performance: since they don't know any bandwidths, they
3470 end up choosing at random rather than weighting their choice by
3471 speed. Fixed by the above feature of putting bandwidths in the
3474 o Major bugfixes (relays):
3475 - Relays were falling out of the networkstatus consensus for
3476 part of a day if they changed their local config but the
3477 authorities discarded their new descriptor as "not sufficiently
3478 different". Now directory authorities accept a descriptor as changed
3479 if BandwidthRate or BandwidthBurst changed. Partial fix for bug 962;
3481 - Ensure that two circuits can never exist on the same connection
3482 with the same circuit ID, even if one is marked for close. This
3483 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
3484 - Directory authorities were neglecting to mark relays down in their
3485 internal histories if the relays fall off the routerlist without
3486 ever being found unreachable. So there were relays in the histories
3487 that haven't been seen for eight months, and are listed as being
3488 up for eight months. This wreaked havoc on the "median wfu" and
3489 "median mtbf" calculations, in turn making Guard and Stable flags
3490 wrong, hurting network performance. Fixes bugs 696 and 969. Bugfix
3493 o Major bugfixes (hidden services):
3494 - When establishing a hidden service, introduction points that
3495 originate from cannibalized circuits were completely ignored
3496 and not included in rendezvous service descriptors. This might
3497 have been another reason for delay in making a hidden service
3498 available. Bugfix from long ago (0.0.9.x?)
3500 o Major bugfixes (memory and resource management):
3501 - Fixed some memory leaks -- some quite frequent, some almost
3502 impossible to trigger -- based on results from Coverity.
3503 - Speed up parsing and cut down on memory fragmentation by using
3504 stack-style allocations for parsing directory objects. Previously,
3505 this accounted for over 40% of allocations from within Tor's code
3506 on a typical directory cache.
3507 - Use a Bloom filter rather than a digest-based set to track which
3508 descriptors we need to keep around when we're cleaning out old
3509 router descriptors. This speeds up the computation significantly,
3510 and may reduce fragmentation.
3512 o New/changed config options:
3513 - Now NodeFamily and MyFamily config options allow spaces in
3514 identity fingerprints, so it's easier to paste them in.
3515 Suggested by Lucky Green.
3516 - Allow ports 465 and 587 in the default exit policy again. We had
3517 rejected them in 0.1.0.15, because back in 2005 they were commonly
3518 misconfigured and ended up as spam targets. We hear they are better
3519 locked down these days.
3520 - Make TrackHostExit mappings expire a while after their last use, not
3521 after their creation. Patch from Robert Hogan.
3522 - Add an ExcludeExitNodes option so users can list a set of nodes
3523 that should be be excluded from the exit node position, but
3524 allowed elsewhere. Implements proposal 151.
3525 - New --hush command-line option similar to --quiet. While --quiet
3526 disables all logging to the console on startup, --hush limits the
3527 output to messages of warning and error severity.
3528 - New configure/torrc options (--enable-geoip-stats,
3529 DirRecordUsageByCountry) to record how many IPs we've served
3530 directory info to in each country code, how many status documents
3531 total we've sent to each country code, and what share of the total
3532 directory requests we should expect to see.
3533 - Make outbound DNS packets respect the OutboundBindAddress setting.
3534 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
3535 - Allow separate log levels to be configured for different logging
3536 domains. For example, this allows one to log all notices, warnings,
3537 or errors, plus all memory management messages of level debug or
3538 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
3539 - Update to the "June 3 2009" ip-to-country file.
3541 o Minor features (relays):
3542 - Raise the minimum rate limiting to be a relay from 20000 bytes
3543 to 20480 bytes (aka 20KB/s), to match our documentation. Also
3544 update directory authorities so they always assign the Fast flag
3545 to relays with 20KB/s of capacity. Now people running relays won't
3546 suddenly find themselves not seeing any use, if the network gets
3548 - If we're a relay and we change our IP address, be more verbose
3549 about the reason that made us change. Should help track down
3550 further bugs for relays on dynamic IP addresses.
3551 - Exit servers can now answer resolve requests for ip6.arpa addresses.
3552 - Implement most of Proposal 152: allow specialized servers to permit
3553 single-hop circuits, and clients to use those servers to build
3554 single-hop circuits when using a specialized controller. Patch
3555 from Josh Albrecht. Resolves feature request 768.
3556 - When relays do their initial bandwidth measurement, don't limit
3557 to just our entry guards for the test circuits. Otherwise we tend
3558 to have multiple test circuits going through a single entry guard,
3559 which makes our bandwidth test less accurate. Fixes part of bug 654;
3560 patch contributed by Josh Albrecht.
3562 o Minor features (directory authorities):
3563 - Try not to open more than one descriptor-downloading connection
3564 to an authority at once. This should reduce load on directory
3565 authorities. Fixes bug 366.
3566 - Add cross-certification to newly generated certificates, so that
3567 a signing key is enough information to look up a certificate. Start
3568 serving certificates by <identity digest, signing key digest>
3569 pairs. Implements proposal 157.
3570 - When a directory authority downloads a descriptor that it then
3571 immediately rejects, do not retry downloading it right away. Should
3572 save some bandwidth on authorities. Fix for bug 888. Patch by
3574 - Directory authorities now serve a /tor/dbg-stability.txt URL to
3575 help debug WFU and MTBF calculations.
3576 - In directory authorities' approved-routers files, allow
3577 fingerprints with or without space.
3579 o Minor features (directory mirrors):
3580 - When a download gets us zero good descriptors, do not notify
3581 Tor that new directory information has arrived.
3582 - Servers support a new URL scheme for consensus downloads that
3583 allows the client to specify which authorities are trusted.
3584 The server then only sends the consensus if the client will trust
3585 it. Otherwise a 404 error is sent back. Clients use this
3586 new scheme when the server supports it (meaning it's running
3587 0.2.1.1-alpha or later). Implements proposal 134.
3589 o Minor features (bridges):
3590 - If the bridge config line doesn't specify a port, assume 443.
3591 This makes bridge lines a bit smaller and easier for users to
3593 - If we're using bridges and our network goes away, be more willing
3594 to forgive our bridges and try again when we get an application
3597 o Minor features (hidden services):
3598 - When the client launches an introduction circuit, retry with a
3599 new circuit after 30 seconds rather than 60 seconds.
3600 - Launch a second client-side introduction circuit in parallel
3601 after a delay of 15 seconds (based on work by Christian Wilms).
3602 - Hidden services start out building five intro circuits rather
3603 than three, and when the first three finish they publish a service
3604 descriptor using those. Now we publish our service descriptor much
3605 faster after restart.
3606 - Drop the requirement to have an open dir port for storing and
3607 serving v2 hidden service descriptors.
3609 o Minor features (build and packaging):
3610 - On Linux, use the prctl call to re-enable core dumps when the User
3612 - Try to make sure that the version of Libevent we're running with
3613 is binary-compatible with the one we built with. May address bug
3615 - Add a new --enable-local-appdata configuration switch to change
3616 the default location of the datadir on win32 from APPDATA to
3617 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
3618 entirely. Patch from coderman.
3619 - Build correctly against versions of OpenSSL 0.9.8 or later that
3620 are built without support for deprecated functions.
3621 - On platforms with a maximum syslog string length, truncate syslog
3622 messages to that length ourselves, rather than relying on the
3623 system to do it for us.
3624 - Automatically detect MacOSX versions earlier than 10.4.0, and
3625 disable kqueue from inside Tor when running with these versions.
3626 We previously did this from the startup script, but that was no
3627 help to people who didn't use the startup script. Resolves bug 863.
3628 - Build correctly when configured to build outside the main source
3629 path. Patch from Michael Gold.
3630 - Disable GCC's strict alias optimization by default, to avoid the
3631 likelihood of its introducing subtle bugs whenever our code violates
3632 the letter of C99's alias rules.
3633 - Change the contrib/tor.logrotate script so it makes the new
3634 logs as "_tor:_tor" rather than the default, which is generally
3635 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
3636 - Change our header file guard macros to be less likely to conflict
3637 with system headers. Adam Langley noticed that we were conflicting
3638 with log.h on Android.
3639 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
3640 and stop using a warning that had become unfixably verbose under
3642 - Use a lockfile to make sure that two Tor processes are not
3643 simultaneously running with the same datadir.
3644 - Allow OpenSSL to use dynamic locks if it wants.
3645 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
3647 o Minor features (controllers):
3648 - When generating circuit events with verbose nicknames for
3649 controllers, try harder to look up nicknames for routers on a
3650 circuit. (Previously, we would look in the router descriptors we had
3651 for nicknames, but not in the consensus.) Partial fix for bug 941.
3652 - New controller event NEWCONSENSUS that lists the networkstatus
3653 lines for every recommended relay. Now controllers like Torflow
3654 can keep up-to-date on which relays they should be using.
3655 - New controller event "clients_seen" to report a geoip-based summary
3656 of which countries we've seen clients from recently. Now controllers
3657 like Vidalia can show bridge operators that they're actually making
3659 - Add a 'getinfo status/clients-seen' controller command, in case
3660 controllers want to hear clients_seen events but connect late.
3661 - New CONSENSUS_ARRIVED event to note when a new consensus has
3662 been fetched and validated.
3663 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
3664 controllers to prevent SIGHUP from reloading the configuration.
3666 - Return circuit purposes in response to GETINFO circuit-status.
3668 - Serve the latest v3 networkstatus consensus via the control
3669 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
3670 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
3671 controller can query our current bootstrap state in case it attaches
3672 partway through and wants to catch up.
3673 - Provide circuit purposes along with circuit events to the controller.
3675 o Minor features (tools):
3676 - Do not have tor-resolve automatically refuse all .onion addresses;
3677 if AutomapHostsOnResolve is set in your torrc, this will work fine.
3678 - Add a -p option to tor-resolve for specifying the SOCKS port: some
3679 people find host:port too confusing.
3680 - Print the SOCKS5 error message string as well as the error code
3681 when a tor-resolve request fails. Patch from Jacob.
3683 o Minor bugfixes (memory and resource management):
3684 - Clients no longer cache certificates for authorities they do not
3685 recognize. Bugfix on 0.2.0.9-alpha.
3686 - Do not use C's stdio library for writing to log files. This will
3687 improve logging performance by a minute amount, and will stop
3688 leaking fds when our disk is full. Fixes bug 861.
3689 - Stop erroneous use of O_APPEND in cases where we did not in fact
3690 want to re-seek to the end of a file before every last write().
3691 - Fix a small alignment and memory-wasting bug on buffer chunks.
3693 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
3694 to avoid unused RAM in buffer chunks and memory pools.
3695 - Reduce the default smartlist size from 32 to 16; it turns out that
3696 most smartlists hold around 8-12 elements tops.
3697 - Make dumpstats() log the fullness and size of openssl-internal
3699 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
3700 patch to their OpenSSL, turn it on to save memory on servers. This
3701 patch will (with any luck) get included in a mainline distribution
3703 - Fix a memory leak when v3 directory authorities load their keys
3704 and cert from disk. Bugfix on 0.2.0.1-alpha.
3705 - Stop using malloc_usable_size() to use more area than we had
3706 actually allocated: it was safe, but made valgrind really unhappy.
3707 - Make the assert_circuit_ok() function work correctly on circuits that
3708 have already been marked for close.
3709 - Fix uninitialized size field for memory area allocation: may improve
3710 memory performance during directory parsing.
3712 o Minor bugfixes (clients):
3713 - Stop reloading the router list from disk for no reason when we
3714 run out of reachable directory mirrors. Once upon a time reloading
3715 it would set the 'is_running' flag back to 1 for them. It hasn't
3716 done that for a long time.
3717 - When we had picked an exit node for a connection, but marked it as
3718 "optional", and it turned out we had no onion key for the exit,
3719 stop wanting that exit and try again. This situation may not
3720 be possible now, but will probably become feasible with proposal
3721 158. Spotted by rovv. Fixes another case of bug 752.
3722 - Fix a bug in address parsing that was preventing bridges or hidden
3723 service targets from being at IPv6 addresses.
3724 - Do not remove routers as too old if we do not have any consensus
3725 document. Bugfix on 0.2.0.7-alpha.
3726 - When an exit relay resolves a stream address to a local IP address,
3727 do not just keep retrying that same exit relay over and
3728 over. Instead, just close the stream. Addresses bug 872. Bugfix
3729 on 0.2.0.32. Patch from rovv.
3730 - Made Tor a little less aggressive about deleting expired
3731 certificates. Partial fix for bug 854.
3732 - Treat duplicate certificate fetches as failures, so that we do
3733 not try to re-fetch an expired certificate over and over and over.
3734 - Do not say we're fetching a certificate when we'll in fact skip it
3735 because of a pending download.
3736 - If we have correct permissions on $datadir, we complain to stdout
3737 and fail to start. But dangerous permissions on
3738 $datadir/cached-status/ would cause us to open a log and complain
3739 there. Now complain to stdout and fail to start in both cases. Fixes
3740 bug 820, reported by seeess.
3742 o Minor bugfixes (bridges):
3743 - When we made bridge authorities stop serving bridge descriptors over
3744 unencrypted links, we also broke DirPort reachability testing for
3745 bridges. So bridges with a non-zero DirPort were printing spurious
3746 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
3747 - Don't allow a bridge to publish its router descriptor to a
3748 non-bridge directory authority. Fixes part of bug 932.
3749 - When we change to or from being a bridge, reset our counts of
3750 client usage by country. Fixes bug 932.
3752 o Minor bugfixes (relays):
3753 - Log correct error messages for DNS-related network errors on
3755 - Actually return -1 in the error case for read_bandwidth_usage().
3756 Harmless bug, since we currently don't care about the return value
3757 anywhere. Bugfix on 0.2.0.9-alpha.
3758 - Provide a more useful log message if bug 977 (related to buffer
3759 freelists) ever reappears, and do not crash right away.
3760 - We were already rejecting relay begin cells with destination port
3761 of 0. Now also reject extend cells with destination port or address
3762 of 0. Suggested by lark.
3763 - When we can't transmit a DNS request due to a network error, retry
3764 it after a while, and eventually transmit a failing response to
3765 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
3766 - Solve a bug that kept hardware crypto acceleration from getting
3767 enabled when accounting was turned on. Fixes bug 907. Bugfix on
3769 - When a canonical connection appears later in our internal list
3770 than a noncanonical one for a given OR ID, always use the
3771 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
3773 - Avoid some nasty corner cases in the logic for marking connections
3774 as too old or obsolete or noncanonical for circuits. Partial
3776 - Fix another interesting corner-case of bug 891 spotted by rovv:
3777 Previously, if two hosts had different amounts of clock drift, and
3778 one of them created a new connection with just the wrong timing,
3779 the other might decide to deprecate the new connection erroneously.
3780 Bugfix on 0.1.1.13-alpha.
3781 - If one win32 nameserver fails to get added, continue adding the
3782 rest, and don't automatically fail.
3783 - Fix a bug where an unreachable relay would establish enough
3784 reachability testing circuits to do a bandwidth test -- if
3785 we already have a connection to the middle hop of the testing
3786 circuit, then it could establish the last hop by using the existing
3787 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
3788 circuits no longer use entry guards in 0.2.1.3-alpha.
3790 o Minor bugfixes (directory authorities):
3791 - Limit uploaded directory documents to be 16M rather than 500K.
3792 The directory authorities were refusing v3 consensus votes from
3793 other authorities, since the votes are now 504K. Fixes bug 959;
3794 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
3795 - Directory authorities should never send a 503 "busy" response to
3796 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
3798 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
3799 headers. Bugfix on 0.2.0.10-alpha.
3801 o Minor bugfixes (hidden services):
3802 - When we can't find an intro key for a v2 hidden service descriptor,
3803 fall back to the v0 hidden service descriptor and log a bug message.
3804 Workaround for bug 1024.
3805 - In very rare situations new hidden service descriptors were
3806 published earlier than 30 seconds after the last change to the
3807 service. (We currently think that a hidden service descriptor
3808 that's been stable for 30 seconds is worth publishing.)
3809 - If a hidden service sends us an END cell, do not consider
3810 retrying the connection; just close it. Patch from rovv.
3811 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
3812 service directories if they have no advertised dir port. Bugfix
3815 o Minor bugfixes (tools):
3816 - In the torify(1) manpage, mention that tsocks will leak your
3819 o Minor bugfixes (controllers):
3820 - If the controller claimed responsibility for a stream, but that
3821 stream never finished making its connection, it would live
3822 forever in circuit_wait state. Now we close it after SocksTimeout
3823 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
3824 - Make DNS resolved controller events into "CLOSED", not
3825 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
3827 - The control port would close the connection before flushing long
3828 replies, such as the network consensus, if a QUIT command was issued
3829 before the reply had completed. Now, the control port flushes all
3830 pending replies before closing the connection. Also fix a spurious
3831 warning when a QUIT command is issued after a malformed or rejected
3832 AUTHENTICATE command, but before the connection was closed. Patch
3833 by Marcus Griep. Fixes bugs 1015 and 1016.
3834 - Fix a bug that made stream bandwidth get misreported to the
3837 o Deprecated and removed features:
3838 - The old "tor --version --version" command, which would print out
3839 the subversion "Id" of most of the source files, is now removed. It
3840 turned out to be less useful than we'd expected, and harder to
3842 - RedirectExits has been removed. It was deprecated since
3844 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
3845 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
3846 - Cell pools are now always enabled; --disable-cell-pools is ignored.
3847 - Directory mirrors no longer fetch the v1 directory or
3848 running-routers files. They are obsolete, and nobody asks for them
3849 anymore. This is the first step to making v1 authorities obsolete.
3850 - Take out the TestVia config option, since it was a workaround for
3851 a bug that was fixed in Tor 0.1.1.21.
3852 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
3853 HiddenServiceExcludeNodes as obsolete: they never worked properly,
3854 and nobody seems to be using them. Fixes bug 754. Bugfix on
3855 0.1.0.1-rc. Patch from Christian Wilms.
3856 - Remove all backward-compatibility code for relays running
3857 versions of Tor so old that they no longer work at all on the
3860 o Code simplifications and refactoring:
3861 - Tool-assisted documentation cleanup. Nearly every function or
3862 static variable in Tor should have its own documentation now.
3863 - Rename the confusing or_is_obsolete field to the more appropriate
3864 is_bad_for_new_circs, and move it to or_connection_t where it
3866 - Move edge-only flags from connection_t to edge_connection_t: not
3867 only is this better coding, but on machines of plausible alignment,
3868 it should save 4-8 bytes per connection_t. "Every little bit helps."
3869 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
3870 for consistency; keep old option working for backward compatibility.
3871 - Simplify the code for finding connections to use for a circuit.
3872 - Revise the connection_new functions so that a more typesafe variant
3873 exists. This will work better with Coverity, and let us find any
3874 actual mistakes we're making here.
3875 - Refactor unit testing logic so that dmalloc can be used sensibly
3876 with unit tests to check for memory leaks.
3877 - Move all hidden-service related fields from connection and circuit
3878 structure to substructures: this way they won't eat so much memory.
3879 - Squeeze 2-5% out of client performance (according to oprofile) by
3880 improving the implementation of some policy-manipulation functions.
3881 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
3882 be more efficient. Formerly it was quadratic in the number of
3883 servers; now it should be linear. Fixes bug 509.
3884 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
3885 and n_conn_id_digest fields into a separate structure that's
3886 only needed when the circuit has not yet attached to an n_conn.
3887 - Optimize out calls to time(NULL) that occur for every IO operation,
3888 or for every cell. On systems like Windows where time() is a
3889 slow syscall, this fix will be slightly helpful.
3892 Changes in version 0.2.0.35 - 2009-06-24
3894 - Avoid crashing in the presence of certain malformed descriptors.
3895 Found by lark, and by automated fuzzing.
3896 - Fix an edge case where a malicious exit relay could convince a
3897 controller that the client's DNS question resolves to an internal IP
3898 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
3901 - Finally fix the bug where dynamic-IP relays disappear when their
3902 IP address changes: directory mirrors were mistakenly telling
3903 them their old address if they asked via begin_dir, so they
3904 never got an accurate answer about their new address, so they
3905 just vanished after a day. For belt-and-suspenders, relays that
3906 don't set Address in their config now avoid using begin_dir for
3907 all direct connections. Should fix bugs 827, 883, and 900.
3908 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
3909 that would occur on some exit nodes when DNS failures and timeouts
3910 occurred in certain patterns. Fix for bug 957.
3913 - When starting with a cache over a few days old, do not leak
3914 memory for the obsolete router descriptors in it. Bugfix on
3915 0.2.0.33; fixes bug 672.
3916 - Hidden service clients didn't use a cached service descriptor that
3917 was older than 15 minutes, but wouldn't fetch a new one either,
3918 because there was already one in the cache. Now, fetch a v2
3919 descriptor unless the same descriptor was added to the cache within
3920 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
3923 Changes in version 0.2.0.34 - 2009-02-08
3924 Tor 0.2.0.34 features several more security-related fixes. You should
3925 upgrade, especially if you run an exit relay (remote crash) or a
3926 directory authority (remote infinite loop), or you're on an older
3927 (pre-XP) or not-recently-patched Windows (remote exploit).
3929 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
3930 have many known flaws, and nobody should be using them. You should
3931 upgrade. If you're using a Linux or BSD and its packages are obsolete,
3932 stop using those packages and upgrade anyway.
3935 - Fix an infinite-loop bug on handling corrupt votes under certain
3936 circumstances. Bugfix on 0.2.0.8-alpha.
3937 - Fix a temporary DoS vulnerability that could be performed by
3938 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
3939 - Avoid a potential crash on exit nodes when processing malformed
3940 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
3941 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
3942 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
3945 - Fix compilation on systems where time_t is a 64-bit integer.
3946 Patch from Matthias Drochner.
3947 - Don't consider expiring already-closed client connections. Fixes
3948 bug 893. Bugfix on 0.0.2pre20.
3951 Changes in version 0.2.0.33 - 2009-01-21
3952 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
3953 useful to users. It also finally fixes a bug where a relay or client
3954 that's been off for many days would take a long time to bootstrap.
3956 This update also fixes an important security-related bug reported by
3957 Ilja van Sprundel. You should upgrade. (We'll send out more details
3958 about the bug once people have had some time to upgrade.)
3961 - Fix a heap-corruption bug that may be remotely triggerable on
3962 some platforms. Reported by Ilja van Sprundel.
3965 - When a stream at an exit relay is in state "resolving" or
3966 "connecting" and it receives an "end" relay cell, the exit relay
3967 would silently ignore the end cell and not close the stream. If
3968 the client never closes the circuit, then the exit relay never
3969 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
3971 - When sending CREATED cells back for a given circuit, use a 64-bit
3972 connection ID to find the right connection, rather than an addr:port
3973 combination. Now that we can have multiple OR connections between
3974 the same ORs, it is no longer possible to use addr:port to uniquely
3975 identify a connection.
3976 - Bridge relays that had DirPort set to 0 would stop fetching
3977 descriptors shortly after startup, and then briefly resume
3978 after a new bandwidth test and/or after publishing a new bridge
3979 descriptor. Bridge users that try to bootstrap from them would
3980 get a recent networkstatus but would get descriptors from up to
3981 18 hours earlier, meaning most of the descriptors were obsolete
3982 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
3983 - Prevent bridge relays from serving their 'extrainfo' document
3984 to anybody who asks, now that extrainfo docs include potentially
3985 sensitive aggregated client geoip summaries. Bugfix on
3987 - If the cached networkstatus consensus is more than five days old,
3988 discard it rather than trying to use it. In theory it could be
3989 useful because it lists alternate directory mirrors, but in practice
3990 it just means we spend many minutes trying directory mirrors that
3991 are long gone from the network. Also discard router descriptors as
3992 we load them if they are more than five days old, since the onion
3993 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
3996 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
3997 could make gcc generate non-functional binary search code. Bugfix
3999 - Build correctly on platforms without socklen_t.
4000 - Compile without warnings on solaris.
4001 - Avoid potential crash on internal error during signature collection.
4002 Fixes bug 864. Patch from rovv.
4003 - Correct handling of possible malformed authority signing key
4004 certificates with internal signature types. Fixes bug 880.
4005 Bugfix on 0.2.0.3-alpha.
4006 - Fix a hard-to-trigger resource leak when logging credential status.
4008 - When we can't initialize DNS because the network is down, do not
4009 automatically stop Tor from starting. Instead, we retry failed
4010 dns_init() every 10 minutes, and change the exit policy to reject
4011 *:* until one succeeds. Fixes bug 691.
4012 - Use 64 bits instead of 32 bits for connection identifiers used with
4013 the controller protocol, to greatly reduce risk of identifier reuse.
4014 - When we're choosing an exit node for a circuit, and we have
4015 no pending streams, choose a good general exit rather than one that
4016 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
4017 - Fix another case of assuming, when a specific exit is requested,
4018 that we know more than the user about what hosts it allows.
4019 Fixes one case of bug 752. Patch from rovv.
4020 - Clip the MaxCircuitDirtiness config option to a minimum of 10
4021 seconds. Warn the user if lower values are given in the
4022 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
4023 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
4024 user if lower values are given in the configuration. Bugfix on
4025 0.1.1.17-rc. Patch by Sebastian.
4026 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
4027 the cache because we already had a v0 descriptor with the same ID.
4028 Bugfix on 0.2.0.18-alpha.
4029 - Fix a race condition when freeing keys shared between main thread
4030 and CPU workers that could result in a memory leak. Bugfix on
4031 0.1.0.1-rc. Fixes bug 889.
4032 - Send a valid END cell back when a client tries to connect to a
4033 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
4034 840. Patch from rovv.
4035 - Check which hops rendezvous stream cells are associated with to
4036 prevent possible guess-the-streamid injection attacks from
4037 intermediate hops. Fixes another case of bug 446. Based on patch
4039 - If a broken client asks a non-exit router to connect somewhere,
4040 do not even do the DNS lookup before rejecting the connection.
4041 Fixes another case of bug 619. Patch from rovv.
4042 - When a relay gets a create cell it can't decrypt (e.g. because it's
4043 using the wrong onion key), we were dropping it and letting the
4044 client time out. Now actually answer with a destroy cell. Fixes
4045 bug 904. Bugfix on 0.0.2pre8.
4047 o Minor bugfixes (hidden services):
4048 - Do not throw away existing introduction points on SIGHUP. Bugfix on
4049 0.0.6pre1. Patch by Karsten. Fixes bug 874.
4052 - Report the case where all signatures in a detached set are rejected
4053 differently than the case where there is an error handling the
4055 - When we realize that another process has modified our cached
4056 descriptors, print out a more useful error message rather than
4057 triggering an assertion. Fixes bug 885. Patch from Karsten.
4058 - Implement the 0x20 hack to better resist DNS poisoning: set the
4059 case on outgoing DNS requests randomly, and reject responses that do
4060 not match the case correctly. This logic can be disabled with the
4061 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
4062 of servers that do not reliably preserve case in replies. See
4063 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
4065 - Check DNS replies for more matching fields to better resist DNS
4067 - Never use OpenSSL compression: it wastes RAM and CPU trying to
4068 compress cells, which are basically all encrypted, compressed, or
4072 Changes in version 0.2.0.32 - 2008-11-20
4073 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
4074 packages (and maybe other packages) noticed by Theo de Raadt, fixes
4075 a smaller security flaw that might allow an attacker to access local
4076 services, further improves hidden service performance, and fixes a
4077 variety of other issues.
4080 - The "User" and "Group" config options did not clear the
4081 supplementary group entries for the Tor process. The "User" option
4082 is now more robust, and we now set the groups to the specified
4083 user's primary group. The "Group" option is now ignored. For more
4084 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
4085 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
4086 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
4087 - The "ClientDNSRejectInternalAddresses" config option wasn't being
4088 consistently obeyed: if an exit relay refuses a stream because its
4089 exit policy doesn't allow it, we would remember what IP address
4090 the relay said the destination address resolves to, even if it's
4091 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
4094 - Fix a DOS opportunity during the voting signature collection process
4095 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
4097 o Major bugfixes (hidden services):
4098 - When fetching v0 and v2 rendezvous service descriptors in parallel,
4099 we were failing the whole hidden service request when the v0
4100 descriptor fetch fails, even if the v2 fetch is still pending and
4101 might succeed. Similarly, if the last v2 fetch fails, we were
4102 failing the whole hidden service request even if a v0 fetch is
4103 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
4104 - When extending a circuit to a hidden service directory to upload a
4105 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
4106 requests failed, because the router descriptor has not been
4107 downloaded yet. In these cases, do not attempt to upload the
4108 rendezvous descriptor, but wait until the router descriptor is
4109 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
4110 descriptor from a hidden service directory for which the router
4111 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
4115 - Fix several infrequent memory leaks spotted by Coverity.
4116 - When testing for libevent functions, set the LDFLAGS variable
4117 correctly. Found by Riastradh.
4118 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
4119 bootstrapping with tunneled directory connections. Bugfix on
4120 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
4121 - When asked to connect to A.B.exit:80, if we don't know the IP for A
4122 and we know that server B rejects most-but-not all connections to
4123 port 80, we would previously reject the connection. Now, we assume
4124 the user knows what they were asking for. Fixes bug 752. Bugfix
4125 on 0.0.9rc5. Diagnosed by BarkerJr.
4126 - If we overrun our per-second write limits a little, count this as
4127 having used up our write allocation for the second, and choke
4128 outgoing directory writes. Previously, we had only counted this when
4129 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
4130 Bugfix on 0.2.0.x (??).
4131 - Remove the old v2 directory authority 'lefkada' from the default
4132 list. It has been gone for many months.
4133 - Stop doing unaligned memory access that generated bus errors on
4134 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
4135 - Make USR2 log-level switch take effect immediately. Bugfix on
4138 o Minor bugfixes (controller):
4139 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
4140 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
4143 Changes in version 0.2.0.31 - 2008-09-03
4144 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
4145 a big bug we're seeing where in rare cases traffic from one Tor stream
4146 gets mixed into another stream, and fixes a variety of smaller issues.
4149 - Make sure that two circuits can never exist on the same connection
4150 with the same circuit ID, even if one is marked for close. This
4151 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
4152 - Relays now reject risky extend cells: if the extend cell includes
4153 a digest of all zeroes, or asks to extend back to the relay that
4154 sent the extend cell, tear down the circuit. Ideas suggested
4156 - If not enough of our entry guards are available so we add a new
4157 one, we might use the new one even if it overlapped with the
4158 current circuit's exit relay (or its family). Anonymity bugfix
4159 pointed out by rovv.
4162 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
4163 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
4164 - Correctly detect the presence of the linux/netfilter_ipv4.h header
4165 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
4166 - Pick size of default geoip filename string correctly on windows.
4167 Fixes bug 806. Bugfix on 0.2.0.30.
4168 - Make the autoconf script accept the obsolete --with-ssl-dir
4169 option as an alias for the actually-working --with-openssl-dir
4170 option. Fix the help documentation to recommend --with-openssl-dir.
4171 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
4172 - When using the TransPort option on OpenBSD, and using the User
4173 option to change UID and drop privileges, make sure to open
4174 /dev/pf before dropping privileges. Fixes bug 782. Patch from
4175 Christopher Davis. Bugfix on 0.1.2.1-alpha.
4176 - Try to attach connections immediately upon receiving a RENDEZVOUS2
4177 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
4178 on the client side when connecting to a hidden service. Bugfix
4179 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
4180 - When closing an application-side connection because its circuit is
4181 getting torn down, generate the stream event correctly. Bugfix on
4182 0.1.2.x. Anonymous patch.
4185 Changes in version 0.2.0.30 - 2008-07-15
4186 This new stable release switches to a more efficient directory
4187 distribution design, adds features to make connections to the Tor
4188 network harder to block, allows Tor to act as a DNS proxy, adds separate
4189 rate limiting for relayed traffic to make it easier for clients to
4190 become relays, fixes a variety of potential anonymity problems, and
4191 includes the usual huge pile of other features and bug fixes.
4193 o New v3 directory design:
4194 - Tor now uses a new way to learn about and distribute information
4195 about the network: the directory authorities vote on a common
4196 network status document rather than each publishing their own
4197 opinion. Now clients and caches download only one networkstatus
4198 document to bootstrap, rather than downloading one for each
4199 authority. Clients only download router descriptors listed in
4200 the consensus. Implements proposal 101; see doc/spec/dir-spec.txt
4202 - Set up moria1, tor26, and dizum as v3 directory authorities
4203 in addition to being v2 authorities. Also add three new ones:
4204 ides (run by Mike Perry), gabelmoo (run by Karsten Loesing), and
4205 dannenberg (run by CCC).
4206 - Switch to multi-level keys for directory authorities: now their
4207 long-term identity key can be kept offline, and they periodically
4208 generate a new signing key. Clients fetch the "key certificates"
4209 to keep up to date on the right keys. Add a standalone tool
4210 "tor-gencert" to generate key certificates. Implements proposal 103.
4211 - Add a new V3AuthUseLegacyKey config option to make it easier for
4212 v3 authorities to change their identity keys if another bug like
4213 Debian's OpenSSL RNG flaw appears.
4214 - Authorities and caches fetch the v2 networkstatus documents
4215 less often, now that v3 is recommended.
4217 o Make Tor connections stand out less on the wire:
4218 - Use an improved TLS handshake designed by Steven Murdoch in proposal
4219 124, as revised in proposal 130. The new handshake is meant to
4220 be harder for censors to fingerprint, and it adds the ability
4221 to detect certain kinds of man-in-the-middle traffic analysis
4222 attacks. The new handshake format includes version negotiation for
4223 OR connections as described in proposal 105, which will allow us
4224 to improve Tor's link protocol more safely in the future.
4225 - Enable encrypted directory connections by default for non-relays,
4226 so censor tools that block Tor directory connections based on their
4227 plaintext patterns will no longer work. This means Tor works in
4228 certain censored countries by default again.
4229 - Stop including recognizeable strings in the commonname part of
4230 Tor's x509 certificates.
4232 o Implement bridge relays:
4233 - Bridge relays (or "bridges" for short) are Tor relays that aren't
4234 listed in the main Tor directory. Since there is no complete public
4235 list of them, even an ISP that is filtering connections to all the
4236 known Tor relays probably won't be able to block all the bridges.
4237 See doc/design-paper/blocking.pdf and proposal 125 for details.
4238 - New config option BridgeRelay that specifies you want to be a
4239 bridge relay rather than a normal relay. When BridgeRelay is set
4240 to 1, then a) you cache dir info even if your DirPort ins't on,
4241 and b) the default for PublishServerDescriptor is now "bridge"
4242 rather than "v2,v3".
4243 - New config option "UseBridges 1" for clients that want to use bridge
4244 relays instead of ordinary entry guards. Clients then specify
4245 bridge relays by adding "Bridge" lines to their config file. Users
4246 can learn about a bridge relay either manually through word of
4247 mouth, or by one of our rate-limited mechanisms for giving out
4248 bridge addresses without letting an attacker easily enumerate them
4249 all. See https://www.torproject.org/bridges for details.
4250 - Bridge relays behave like clients with respect to time intervals
4251 for downloading new v3 consensus documents -- otherwise they
4252 stand out. Bridge users now wait until the end of the interval,
4253 so their bridge relay will be sure to have a new consensus document.
4255 o Implement bridge directory authorities:
4256 - Bridge authorities are like normal directory authorities, except
4257 they don't serve a list of known bridges. Therefore users that know
4258 a bridge's fingerprint can fetch a relay descriptor for that bridge,
4259 including fetching updates e.g. if the bridge changes IP address,
4260 yet an attacker can't just fetch a list of all the bridges.
4261 - Set up Tonga as the default bridge directory authority.
4262 - Bridge authorities refuse to serve bridge descriptors or other
4263 bridge information over unencrypted connections (that is, when
4264 responding to direct DirPort requests rather than begin_dir cells.)
4265 - Bridge directory authorities do reachability testing on the
4266 bridges they know. They provide router status summaries to the
4267 controller via "getinfo ns/purpose/bridge", and also dump summaries
4268 to a file periodically, so we can keep internal stats about which
4269 bridges are functioning.
4270 - If bridge users set the UpdateBridgesFromAuthority config option,
4271 but the digest they ask for is a 404 on the bridge authority,
4272 they fall back to contacting the bridge directly.
4273 - Bridges always use begin_dir to publish their server descriptor to
4274 the bridge authority using an anonymous encrypted tunnel.
4275 - Early work on a "bridge community" design: if bridge authorities set
4276 the BridgePassword config option, they will serve a snapshot of
4277 known bridge routerstatuses from their DirPort to anybody who
4278 knows that password. Unset by default.
4279 - Tor now includes an IP-to-country GeoIP file, so bridge relays can
4280 report sanitized aggregated summaries in their extra-info documents
4281 privately to the bridge authority, listing which countries are
4282 able to reach them. We hope this mechanism will let us learn when
4283 certain countries start trying to block bridges.
4284 - Bridge authorities write bridge descriptors to disk, so they can
4285 reload them after a reboot. They can also export the descriptors
4286 to other programs, so we can distribute them to blocked users via
4287 the BridgeDB interface, e.g. via https://bridges.torproject.org/
4288 and bridges@torproject.org.
4290 o Tor can be a DNS proxy:
4291 - The new client-side DNS proxy feature replaces the need for
4292 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
4293 for DNS requests on port 9999, use the Tor network to resolve them
4294 anonymously, and send the reply back like a regular DNS server.
4295 The code still only implements a subset of DNS.
4296 - Add a new AutomapHostsOnResolve option: when it is enabled, any
4297 resolve request for hosts matching a given pattern causes Tor to
4298 generate an internal virtual address mapping for that host. This
4299 allows DNSPort to work sensibly with hidden service users. By
4300 default, .exit and .onion addresses are remapped; the list of
4301 patterns can be reconfigured with AutomapHostsSuffixes.
4302 - Add an "-F" option to tor-resolve to force a resolve for a .onion
4303 address. Thanks to the AutomapHostsOnResolve option, this is no
4304 longer a completely silly thing to do.
4306 o Major features (relay usability):
4307 - New config options RelayBandwidthRate and RelayBandwidthBurst:
4308 a separate set of token buckets for relayed traffic. Right now
4309 relayed traffic is defined as answers to directory requests, and
4310 OR connections that don't have any local circuits on them. See
4311 proposal 111 for details.
4312 - Create listener connections before we setuid to the configured
4313 User and Group. Now non-Windows users can choose port values
4314 under 1024, start Tor as root, and have Tor bind those ports
4315 before it changes to another UID. (Windows users could already
4317 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
4318 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
4319 on "vserver" accounts. Patch from coderman.
4321 o Major features (directory authorities):
4322 - Directory authorities track weighted fractional uptime and weighted
4323 mean-time-between failures for relays. WFU is suitable for deciding
4324 whether a node is "usually up", while MTBF is suitable for deciding
4325 whether a node is "likely to stay up." We need both, because
4326 "usually up" is a good requirement for guards, while "likely to
4327 stay up" is a good requirement for long-lived connections.
4328 - Directory authorities use a new formula for selecting which relays
4329 to advertise as Guards: they must be in the top 7/8 in terms of
4330 how long we have known about them, and above the median of those
4331 nodes in terms of weighted fractional uptime.
4332 - Directory authorities use a new formula for selecting which relays
4333 to advertise as Stable: when we have 4 or more days of data, use
4334 median measured MTBF rather than median declared uptime. Implements
4336 - Directory authorities accept and serve "extra info" documents for
4337 routers. Routers now publish their bandwidth-history lines in the
4338 extra-info docs rather than the main descriptor. This step saves
4339 60% (!) on compressed router descriptor downloads. Servers upload
4340 extra-info docs to any authority that accepts them; directory
4341 authorities now allow multiple router descriptors and/or extra
4342 info documents to be uploaded in a single go. Authorities, and
4343 caches that have been configured to download extra-info documents,
4344 download them as needed. Implements proposal 104.
4345 - Authorities now list relays who have the same nickname as
4346 a different named relay, but list them with a new flag:
4347 "Unnamed". Now we can make use of relays that happen to pick the
4348 same nickname as a server that registered two years ago and then
4349 disappeared. Implements proposal 122.
4350 - Store routers in a file called cached-descriptors instead of in
4351 cached-routers. Initialize cached-descriptors from cached-routers
4352 if the old format is around. The new format allows us to store
4353 annotations along with descriptors, to record the time we received
4354 each descriptor, its source, and its purpose: currently one of
4355 general, controller, or bridge.
4357 o Major features (other):
4358 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
4359 Tor can warn and/or refuse connections to ports commonly used with
4360 vulnerable-plaintext protocols. Currently we warn on ports 23,
4361 109, 110, and 143, but we don't reject any. Based on proposal 129
4362 by Kevin Bauer and Damon McCoy.
4363 - Integrate Karsten Loesing's Google Summer of Code project to publish
4364 hidden service descriptors on a set of redundant relays that are a
4365 function of the hidden service address. Now we don't have to rely
4366 on three central hidden service authorities for publishing and
4367 fetching every hidden service descriptor. Implements proposal 114.
4368 - Allow tunnelled directory connections to ask for an encrypted
4369 "begin_dir" connection or an anonymized "uses a full Tor circuit"
4370 connection independently. Now we can make anonymized begin_dir
4371 connections for (e.g.) more secure hidden service posting and
4374 o Major bugfixes (crashes and assert failures):
4375 - Stop imposing an arbitrary maximum on the number of file descriptors
4376 used for busy servers. Bug reported by Olaf Selke; patch from
4378 - Avoid possible failures when generating a directory with routers
4379 with over-long versions strings, or too many flags set.
4380 - Fix a rare assert error when we're closing one of our threads:
4381 use a mutex to protect the list of logs, so we never write to the
4382 list as it's being freed. Fixes the very rare bug 575, which is
4383 kind of the revenge of bug 222.
4384 - Avoid segfault in the case where a badly behaved v2 versioning
4385 directory sends a signed networkstatus with missing client-versions.
4386 - When we hit an EOF on a log (probably because we're shutting down),
4387 don't try to remove the log from the list: just mark it as
4388 unusable. (Bulletproofs against bug 222.)
4390 o Major bugfixes (code security fixes):
4391 - Detect size overflow in zlib code. Reported by Justin Ferguson and
4393 - Rewrite directory tokenization code to never run off the end of
4394 a string. Fixes bug 455. Patch from croup.
4395 - Be more paranoid about overwriting sensitive memory on free(),
4396 as a defensive programming tactic to ensure forward secrecy.
4398 o Major bugfixes (anonymity fixes):
4399 - Reject requests for reverse-dns lookup of names that are in
4400 a private address space. Patch from lodger.
4401 - Never report that we've used more bandwidth than we're willing to
4402 relay: it leaks how much non-relay traffic we're using. Resolves
4404 - As a client, do not believe any server that tells us that an
4405 address maps to an internal address space.
4406 - Warn about unsafe ControlPort configurations.
4407 - Directory authorities now call routers Fast if their bandwidth is
4408 at least 100KB/s, and consider their bandwidth adequate to be a
4409 Guard if it is at least 250KB/s, no matter the medians. This fix
4410 complements proposal 107.
4411 - Directory authorities now never mark more than 2 servers per IP as
4412 Valid and Running (or 5 on addresses shared by authorities).
4413 Implements proposal 109, by Kevin Bauer and Damon McCoy.
4414 - If we're a relay, avoid picking ourselves as an introduction point,
4415 a rendezvous point, or as the final hop for internal circuits. Bug
4416 reported by taranis and lodger.
4417 - Exit relays that are used as a client can now reach themselves
4418 using the .exit notation, rather than just launching an infinite
4419 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
4420 - Fix a bug where, when we were choosing the 'end stream reason' to
4421 put in our relay end cell that we send to the exit relay, Tor
4422 clients on Windows were sometimes sending the wrong 'reason'. The
4423 anonymity problem is that exit relays may be able to guess whether
4424 the client is running Windows, thus helping partition the anonymity
4425 set. Down the road we should stop sending reasons to exit relays,
4426 or otherwise prevent future versions of this bug.
4427 - Only update guard status (usable / not usable) once we have
4428 enough directory information. This was causing us to discard all our
4429 guards on startup if we hadn't been running for a few weeks. Fixes
4431 - When our directory information has been expired for a while, stop
4432 being willing to build circuits using it. Fixes bug 401.
4434 o Major bugfixes (peace of mind for relay operators)
4435 - Non-exit relays no longer answer "resolve" relay cells, so they
4436 can't be induced to do arbitrary DNS requests. (Tor clients already
4437 avoid using non-exit relays for resolve cells, but now servers
4438 enforce this too.) Fixes bug 619. Patch from lodger.
4439 - When we setconf ClientOnly to 1, close any current OR and Dir
4440 listeners. Reported by mwenge.
4442 o Major bugfixes (other):
4443 - If we only ever used Tor for hidden service lookups or posts, we
4444 would stop building circuits and start refusing connections after
4445 24 hours, since we falsely believed that Tor was dormant. Reported
4447 - Add a new __HashedControlSessionPassword option for controllers
4448 to use for one-off session password hashes that shouldn't get
4449 saved to disk by SAVECONF --- Vidalia users were accumulating a
4450 pile of HashedControlPassword lines in their torrc files, one for
4451 each time they had restarted Tor and then clicked Save. Make Tor
4452 automatically convert "HashedControlPassword" to this new option but
4453 only when it's given on the command line. Partial fix for bug 586.
4454 - Patch from "Andrew S. Lists" to catch when we contact a directory
4455 mirror at IP address X and he says we look like we're coming from
4456 IP address X. Otherwise this would screw up our address detection.
4457 - Reject uploaded descriptors and extrainfo documents if they're
4458 huge. Otherwise we'll cache them all over the network and it'll
4459 clog everything up. Suggested by Aljosha Judmayer.
4460 - When a hidden service was trying to establish an introduction point,
4461 and Tor *did* manage to reuse one of the preemptively built
4462 circuits, it didn't correctly remember which one it used,
4463 so it asked for another one soon after, until there were no
4464 more preemptive circuits, at which point it launched one from
4465 scratch. Bugfix on 0.0.9.x.
4467 o Rate limiting and load balancing improvements:
4468 - When we add data to a write buffer in response to the data on that
4469 write buffer getting low because of a flush, do not consider the
4470 newly added data as a candidate for immediate flushing, but rather
4471 make it wait until the next round of writing. Otherwise, we flush
4472 and refill recursively, and a single greedy TLS connection can
4473 eat all of our bandwidth.
4474 - When counting the number of bytes written on a TLS connection,
4475 look at the BIO actually used for writing to the network, not
4476 at the BIO used (sometimes) to buffer data for the network.
4477 Looking at different BIOs could result in write counts on the
4478 order of ULONG_MAX. Fixes bug 614.
4479 - If we change our MaxAdvertisedBandwidth and then reload torrc,
4480 Tor won't realize it should publish a new relay descriptor. Fixes
4481 bug 688, reported by mfr.
4482 - Avoid using too little bandwidth when our clock skips a few seconds.
4483 - Choose which bridge to use proportional to its advertised bandwidth,
4484 rather than uniformly at random. This should speed up Tor for
4485 bridge users. Also do this for people who set StrictEntryNodes.
4487 o Bootstrapping faster and building circuits more intelligently:
4488 - Fix bug 660 that was preventing us from knowing that we should
4489 preemptively build circuits to handle expected directory requests.
4490 - When we're checking if we have enough dir info for each relay
4491 to begin establishing circuits, make sure that we actually have
4492 the descriptor listed in the consensus, not just any descriptor.
4493 - Correctly notify one-hop connections when a circuit build has
4494 failed. Possible fix for bug 669. Found by lodger.
4495 - Clients now hold circuitless TLS connections open for 1.5 times
4496 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
4497 rebuild a new circuit over them within that timeframe. Previously,
4498 they held them open only for KeepalivePeriod (5 minutes).
4500 o Performance improvements (memory):
4501 - Add OpenBSD malloc code from "phk" as an optional malloc
4502 replacement on Linux: some glibc libraries do very poorly with
4503 Tor's memory allocation patterns. Pass --enable-openbsd-malloc to
4504 ./configure to get the replacement malloc code.
4505 - Switch our old ring buffer implementation for one more like that
4506 used by free Unix kernels. The wasted space in a buffer with 1mb
4507 of data will now be more like 8k than 1mb. The new implementation
4508 also avoids realloc();realloc(); patterns that can contribute to
4509 memory fragmentation.
4510 - Change the way that Tor buffers data that it is waiting to write.
4511 Instead of queueing data cells in an enormous ring buffer for each
4512 client->OR or OR->OR connection, we now queue cells on a separate
4513 queue for each circuit. This lets us use less slack memory, and
4514 will eventually let us be smarter about prioritizing different kinds
4516 - Reference-count and share copies of address policy entries; only 5%
4517 of them were actually distinct.
4518 - Tune parameters for cell pool allocation to minimize amount of
4520 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
4521 for every single inactive connection_t. Free items from the
4522 4k/16k-buffer free lists when they haven't been used for a while.
4523 - Make memory debugging information describe more about history
4524 of cell allocation, so we can help reduce our memory use.
4525 - Be even more aggressive about releasing RAM from small
4526 empty buffers. Thanks to our free-list code, this shouldn't be too
4527 performance-intensive.
4528 - Log malloc statistics from mallinfo() on platforms where it exists.
4529 - Use memory pools to allocate cells with better speed and memory
4530 efficiency, especially on platforms where malloc() is inefficient.
4531 - Add a --with-tcmalloc option to the configure script to link
4532 against tcmalloc (if present). Does not yet search for non-system
4535 o Performance improvements (socket management):
4536 - Count the number of open sockets separately from the number of
4537 active connection_t objects. This will let us avoid underusing
4538 our allocated connection limit.
4539 - We no longer use socket pairs to link an edge connection to an
4540 anonymous directory connection or a DirPort test connection.
4541 Instead, we track the link internally and transfer the data
4542 in-process. This saves two sockets per "linked" connection (at the
4543 client and at the server), and avoids the nasty Windows socketpair()
4545 - We were leaking a file descriptor if Tor started with a zero-length
4546 cached-descriptors file. Patch by "freddy77".
4548 o Performance improvements (CPU use):
4549 - Never walk through the list of logs if we know that no log target
4550 is interested in a given message.
4551 - Call routerlist_remove_old_routers() much less often. This should
4552 speed startup, especially on directory caches.
4553 - Base64 decoding was actually showing up on our profile when parsing
4554 the initial descriptor file; switch to an in-process all-at-once
4555 implementation that's about 3.5x times faster than calling out to
4557 - Use a slightly simpler string hashing algorithm (copying Python's
4558 instead of Java's) and optimize our digest hashing algorithm to take
4559 advantage of 64-bit platforms and to remove some possibly-costly
4561 - When implementing AES counter mode, update only the portions of the
4562 counter buffer that need to change, and don't keep separate
4563 network-order and host-order counters on big-endian hosts (where
4565 - Add an in-place version of aes_crypt() so that we can avoid doing a
4566 needless memcpy() call on each cell payload.
4567 - Use Critical Sections rather than Mutexes for synchronizing threads
4568 on win32; Mutexes are heavier-weight, and designed for synchronizing
4571 o Performance improvements (bandwidth use):
4572 - Don't try to launch new descriptor downloads quite so often when we
4573 already have enough directory information to build circuits.
4574 - Version 1 directories are no longer generated in full. Instead,
4575 authorities generate and serve "stub" v1 directories that list
4576 no servers. This will stop Tor versions 0.1.0.x and earlier from
4577 working, but (for security reasons) nobody should be running those
4579 - Avoid going directly to the directory authorities even if you're a
4580 relay, if you haven't found yourself reachable yet or if you've
4581 decided not to advertise your dirport yet. Addresses bug 556.
4582 - If we've gone 12 hours since our last bandwidth check, and we
4583 estimate we have less than 50KB bandwidth capacity but we could
4584 handle more, do another bandwidth test.
4585 - Support "If-Modified-Since" when answering HTTP requests for
4586 directories, running-routers documents, and v2 and v3 networkstatus
4587 documents. (There's no need to support it for router descriptors,
4588 since those are downloaded by descriptor digest.)
4589 - Stop fetching directory info so aggressively if your DirPort is
4590 on but your ORPort is off; stop fetching v2 dir info entirely.
4591 You can override these choices with the new FetchDirInfoEarly
4594 o Changed config option behavior (features):
4595 - Configuration files now accept C-style strings as values. This
4596 helps encode characters not allowed in the current configuration
4597 file format, such as newline or #. Addresses bug 557.
4598 - Add hidden services and DNSPorts to the list of things that make
4599 Tor accept that it has running ports. Change starting Tor with no
4600 ports from a fatal error to a warning; we might change it back if
4601 this turns out to confuse anybody. Fixes bug 579.
4602 - Make PublishServerDescriptor default to 1, so the default doesn't
4603 have to change as we invent new directory protocol versions.
4604 - Allow people to say PreferTunnelledDirConns rather than
4605 PreferTunneledDirConns, for those alternate-spellers out there.
4606 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
4607 accommodate the growing number of servers that use the default
4608 and are reaching it.
4609 - Make it possible to enable HashedControlPassword and
4610 CookieAuthentication at the same time.
4611 - When a TrackHostExits-chosen exit fails too many times in a row,
4612 stop using it. Fixes bug 437.
4614 o Changed config option behavior (bugfixes):
4615 - Do not read the configuration file when we've only been told to
4616 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
4617 based on patch from Sebastian Hahn.
4618 - Actually validate the options passed to AuthDirReject,
4619 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
4620 - Make "ClientOnly 1" config option disable directory ports too.
4621 - Don't stop fetching descriptors when FetchUselessDescriptors is
4622 set, even if we stop asking for circuits. Bug reported by tup
4624 - Servers used to decline to publish their DirPort if their
4625 BandwidthRate or MaxAdvertisedBandwidth were below a threshold. Now
4626 they look only at BandwidthRate and RelayBandwidthRate.
4627 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
4628 minus 1 byte: the actual maximum declared bandwidth.
4629 - Make "TrackHostExits ." actually work. Bugfix on 0.1.0.x.
4630 - Make the NodeFamilies config option work. (Reported by
4631 lodger -- it has never actually worked, even though we added it
4633 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
4634 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
4636 o New config options:
4637 - New configuration options AuthDirMaxServersPerAddr and
4638 AuthDirMaxServersperAuthAddr to override default maximum number
4639 of servers allowed on a single IP address. This is important for
4640 running a test network on a single host.
4641 - Three new config options (AlternateDirAuthority,
4642 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
4643 user selectively replace the default directory authorities by type,
4644 rather than the all-or-nothing replacement that DirServer offers.
4645 - New config options AuthDirBadDir and AuthDirListBadDirs for
4646 authorities to mark certain relays as "bad directories" in the
4647 networkstatus documents. Also supports the "!baddir" directive in
4648 the approved-routers file.
4649 - New config option V2AuthoritativeDirectory that all v2 directory
4650 authorities must set. This lets v3 authorities choose not to serve
4651 v2 directory information.
4653 o Minor features (other):
4654 - When we're not serving v2 directory information, there is no reason
4655 to actually keep any around. Remove the obsolete files and directory
4656 on startup if they are very old and we aren't going to serve them.
4657 - When we negotiate a v2 link-layer connection (not yet implemented),
4658 accept RELAY_EARLY cells and turn them into RELAY cells if we've
4659 negotiated a v1 connection for their next step. Initial steps for
4661 - When we have no consensus, check FallbackNetworkstatusFile (defaults
4662 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
4663 we can start out knowing some directory caches. We don't ship with
4664 a fallback consensus by default though, because it was making
4665 bootstrapping take too long while we tried many down relays.
4666 - Authorities send back an X-Descriptor-Not-New header in response to
4667 an accepted-but-discarded descriptor upload. Partially implements
4669 - If we find a cached-routers file that's been sitting around for more
4670 than 28 days unmodified, then most likely it's a leftover from
4671 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
4673 - When we (as a cache) download a descriptor because it was listed
4674 in a consensus, remember when the consensus was supposed to expire,
4675 and don't expire the descriptor until then.
4676 - Optionally (if built with -DEXPORTMALLINFO) export the output
4677 of mallinfo via http, as tor/mallinfo.txt. Only accessible
4679 - Tag every guard node in our state file with the version that
4680 we believe added it, or with our own version if we add it. This way,
4681 if a user temporarily runs an old version of Tor and then switches
4682 back to a new one, she doesn't automatically lose her guards.
4683 - When somebody requests a list of statuses or servers, and we have
4684 none of those, return a 404 rather than an empty 200.
4685 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
4687 - Add an HSAuthorityRecordStats option that hidden service authorities
4688 can use to track statistics of overall hidden service usage without
4689 logging information that would be as useful to an attacker.
4690 - Allow multiple HiddenServicePort directives with the same virtual
4691 port; when they occur, the user is sent round-robin to one
4692 of the target ports chosen at random. Partially fixes bug 393 by
4693 adding limited ad-hoc round-robining.
4694 - Revamp file-writing logic so we don't need to have the entire
4695 contents of a file in memory at once before we write to disk. Tor,
4698 o Minor bugfixes (other):
4699 - Alter the code that tries to recover from unhandled write
4700 errors, to not try to flush onto a socket that's given us
4702 - Directory mirrors no longer include a guess at the client's IP
4703 address if the connection appears to be coming from the same /24
4704 network; it was producing too many wrong guesses.
4705 - If we're trying to flush the last bytes on a connection (for
4706 example, when answering a directory request), reset the
4707 time-to-give-up timeout every time we manage to write something
4709 - Reject router descriptors with out-of-range bandwidthcapacity or
4710 bandwidthburst values.
4711 - If we can't expand our list of entry guards (e.g. because we're
4712 using bridges or we have StrictEntryNodes set), don't mark relays
4713 down when they fail a directory request. Otherwise we're too quick
4714 to mark all our entry points down.
4715 - Authorities no longer send back "400 you're unreachable please fix
4716 it" errors to Tor servers that aren't online all the time. We're
4717 supposed to tolerate these servers now.
4718 - Let directory authorities startup even when they can't generate
4719 a descriptor immediately, e.g. because they don't know their
4721 - Correctly enforce that elements of directory objects do not appear
4722 more often than they are allowed to appear.
4723 - Stop allowing hibernating servers to be "stable" or "fast".
4724 - On Windows, we were preventing other processes from reading
4725 cached-routers while Tor was running. (Reported by janbar)
4726 - Check return values from pthread_mutex functions.
4727 - When opening /dev/null in finish_daemonize(), do not pass the
4728 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
4729 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
4731 o Controller features:
4732 - The GETCONF command now escapes and quotes configuration values
4733 that don't otherwise fit into the torrc file.
4734 - The SETCONF command now handles quoted values correctly.
4735 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
4736 ask about source, timestamp of arrival, purpose, etc. We need
4737 something like this to help Vidalia not do GeoIP lookups on bridge
4739 - Allow multiple HashedControlPassword config lines, to support
4740 multiple controller passwords.
4741 - Accept LF instead of CRLF on controller, since some software has a
4742 hard time generating real Internet newlines.
4743 - Add GETINFO values for the server status events
4744 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
4746 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
4747 GETINFO for Torstat to use until it can switch to using extrainfos.
4748 - New config option CookieAuthFile to choose a new location for the
4749 cookie authentication file, and config option
4750 CookieAuthFileGroupReadable to make it group-readable.
4751 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
4752 match requests to applications. Patch from Robert Hogan.
4753 - Add a RESOLVE command to launch hostname lookups. Original patch
4755 - Add GETINFO status/enough-dir-info to let controllers tell whether
4756 Tor has downloaded sufficient directory information. Patch from Tup.
4757 - You can now use the ControlSocket option to tell Tor to listen for
4758 controller connections on Unix domain sockets on systems that
4759 support them. Patch from Peter Palfrader.
4760 - New "GETINFO address-mappings/*" command to get address mappings
4761 with expiry information. "addr-mappings/*" is now deprecated.
4763 - Add a new config option __DisablePredictedCircuits designed for
4764 use by the controller, when we don't want Tor to build any circuits
4766 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
4767 so we can exit from the middle of the circuit.
4768 - Implement "getinfo status/circuit-established".
4769 - Implement "getinfo status/version/..." so a controller can tell
4770 whether the current version is recommended, and whether any versions
4771 are good, and how many authorities agree. Patch from "shibz".
4772 - Controllers should now specify cache=no or cache=yes when using
4773 the +POSTDESCRIPTOR command.
4774 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
4775 Robert Hogan. Fixes the first part of bug 681.
4776 - When reporting clock skew, and we know that the clock is _at least
4777 as skewed_ as some value, but we don't know the actual value,
4778 report the value as a "minimum skew."
4780 o Controller bugfixes:
4781 - Generate "STATUS_SERVER" events rather than misspelled
4782 "STATUS_SEVER" events. Caught by mwenge.
4783 - Reject controller commands over 1MB in length, so rogue
4784 processes can't run us out of memory.
4785 - Change the behavior of "getinfo status/good-server-descriptor"
4786 so it doesn't return failure when any authority disappears.
4787 - Send NAMESERVER_STATUS messages for a single failed nameserver
4789 - When the DANGEROUS_VERSION controller status event told us we're
4790 running an obsolete version, it used the string "OLD" to describe
4791 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
4792 "OBSOLETE" in both cases.
4793 - Respond to INT and TERM SIGNAL commands before we execute the
4794 signal, in case the signal shuts us down. We had a patch in
4795 0.1.2.1-alpha that tried to do this by queueing the response on
4796 the connection's buffer before shutting down, but that really
4797 isn't the same thing at all. Bug located by Matt Edman.
4798 - Provide DNS expiry times in GMT, not in local time. For backward
4799 compatibility, ADDRMAP events only provide GMT expiry in an extended
4800 field. "GETINFO address-mappings" always does the right thing.
4801 - Use CRLF line endings properly in NS events.
4802 - Make 'getinfo fingerprint' return a 551 error if we're not a
4803 server, so we match what the control spec claims we do. Reported
4805 - Fix a typo in an error message when extendcircuit fails that
4806 caused us to not follow the \r\n-based delimiter protocol. Reported
4808 - When tunneling an encrypted directory connection, and its first
4809 circuit fails, do not leave it unattached and ask the controller
4810 to deal. Fixes the second part of bug 681.
4811 - Treat some 403 responses from directory servers as INFO rather than
4812 WARN-severity events.
4814 o Portability / building / compiling:
4815 - When building with --enable-gcc-warnings, check for whether Apple's
4816 warning "-Wshorten-64-to-32" is available.
4817 - Support compilation to target iPhone; patch from cjacker huang.
4818 To build for iPhone, pass the --enable-iphone option to configure.
4819 - Port Tor to build and run correctly on Windows CE systems, using
4820 the wcecompat library. Contributed by Valerio Lupi.
4821 - Detect non-ASCII platforms (if any still exist) and refuse to
4822 build there: some of our code assumes that 'A' is 65 and so on.
4823 - Clear up some MIPSPro compiler warnings.
4824 - Make autoconf search for libevent, openssl, and zlib consistently.
4825 - Update deprecated macros in configure.in.
4826 - When warning about missing headers, tell the user to let us
4827 know if the compile succeeds anyway, so we can downgrade the
4829 - Include the current subversion revision as part of the version
4830 string: either fetch it directly if we're in an SVN checkout, do
4831 some magic to guess it if we're in an SVK checkout, or use
4832 the last-detected version if we're building from a .tar.gz.
4833 Use this version consistently in log messages.
4834 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
4835 - Read resolv.conf files correctly on platforms where read() returns
4836 partial results on small file reads.
4837 - Build without verbose warnings even on gcc 4.2 and 4.3.
4838 - On Windows, correctly detect errors when listing the contents of
4839 a directory. Fix from lodger.
4840 - Run 'make test' as part of 'make dist', so we stop releasing so
4841 many development snapshots that fail their unit tests.
4842 - Add support to detect Libevent versions in the 1.4.x series
4844 - Add command-line arguments to unit-test executable so that we can
4845 invoke any chosen test from the command line rather than having
4846 to run the whole test suite at once; and so that we can turn on
4847 logging for the unit tests.
4848 - Do not automatically run configure from autogen.sh. This
4849 non-standard behavior tended to annoy people who have built other
4851 - Fix a macro/CPP interaction that was confusing some compilers:
4852 some GCCs don't like #if/#endif pairs inside macro arguments.
4854 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
4855 Fixes bug 704; fix from Steven Murdoch.
4856 - Correctly detect transparent proxy support on Linux hosts that
4857 require in.h to be included before netfilter_ipv4.h. Patch
4860 o Logging improvements:
4861 - When we haven't had any application requests lately, don't bother
4862 logging that we have expired a bunch of descriptors.
4863 - When attempting to open a logfile fails, tell us why.
4864 - Only log guard node status when guard node status has changed.
4865 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
4866 make "INFO" 75% less verbose.
4867 - When SafeLogging is disabled, log addresses along with all TLS
4869 - Report TLS "zero return" case as a "clean close" and "IO error"
4870 as a "close". Stop calling closes "unexpected closes": existing
4871 Tors don't use SSL_close(), so having a connection close without
4872 the TLS shutdown handshake is hardly unexpected.
4873 - When we receive a consensus from the future, warn about skew.
4874 - Make "not enough dir info yet" warnings describe *why* Tor feels
4875 it doesn't have enough directory info yet.
4876 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
4877 consumers. (We already do this on HUP.)
4878 - Give more descriptive well-formedness errors for out-of-range
4879 hidden service descriptor/protocol versions.
4880 - Stop recommending that every server operator send mail to tor-ops.
4881 Resolves bug 597. Bugfix on 0.1.2.x.
4882 - Improve skew reporting: try to give the user a better log message
4883 about how skewed they are, and how much this matters.
4884 - New --quiet command-line option to suppress the default console log.
4885 Good in combination with --hash-password.
4886 - Don't complain that "your server has not managed to confirm that its
4887 ports are reachable" if we haven't been able to build any circuits
4889 - Detect the reason for failing to mmap a descriptor file we just
4890 wrote, and give a more useful log message. Fixes bug 533.
4891 - Always prepend "Bug: " to any log message about a bug.
4892 - When dumping memory usage, list bytes used in buffer memory
4894 - When running with dmalloc, dump more stats on hup and on exit.
4895 - Put a platform string (e.g. "Linux i686") in the startup log
4896 message, so when people paste just their logs, we know if it's
4897 OpenBSD or Windows or what.
4898 - When logging memory usage, break down memory used in buffers by
4900 - When we are reporting the DirServer line we just parsed, we were
4901 logging the second stanza of the key fingerprint, not the first.
4902 - Even though Windows is equally happy with / and \ as path separators,
4903 try to use \ consistently on Windows and / consistently on Unix: it
4904 makes the log messages nicer.
4905 - On OSX, stop warning the user that kqueue support in libevent is
4906 "experimental", since it seems to have worked fine for ages.
4908 o Contributed scripts and tools:
4909 - Update linux-tor-prio.sh script to allow QoS based on the uid of
4910 the Tor process. Patch from Marco Bonetti with tweaks from Mike
4912 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
4913 Unix users an easy way to script their Tor process (e.g. by
4914 adjusting bandwidth based on the time of the day).
4915 - In the exitlist script, only consider the most recently published
4916 server descriptor for each server. Also, when the user requests
4917 a list of servers that _reject_ connections to a given address,
4918 explicitly exclude the IPs that also have servers that accept
4919 connections to that address. Resolves bug 405.
4920 - Include a new contrib/tor-exit-notice.html file that exit relay
4921 operators can put on their website to help reduce abuse queries.
4923 o Newly deprecated features:
4924 - The status/version/num-versioning and status/version/num-concurring
4925 GETINFO controller options are no longer useful in the v3 directory
4926 protocol: treat them as deprecated, and warn when they're used.
4927 - The RedirectExits config option is now deprecated.
4930 - Drop the old code to choke directory connections when the
4931 corresponding OR connections got full: thanks to the cell queue
4932 feature, OR conns don't get full any more.
4933 - Remove the old "dns worker" server DNS code: it hasn't been default
4934 since 0.1.2.2-alpha, and all the servers are using the new
4936 - Remove the code to generate the oldest (v1) directory format.
4937 - Remove support for the old bw_accounting file: we've been storing
4938 bandwidth accounting information in the state file since
4939 0.1.2.5-alpha. This may result in bandwidth accounting errors
4940 if you try to upgrade from 0.1.1.x or earlier, or if you try to
4941 downgrade to 0.1.1.x or earlier.
4942 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
4943 it, it had no AES, and it hasn't seen any security patches since
4945 - Stop overloading the circuit_t.onionskin field for both "onionskin
4946 from a CREATE cell that we are waiting for a cpuworker to be
4947 assigned" and "onionskin from an EXTEND cell that we are going to
4948 send to an OR as soon as we are connected". Might help with bug 600.
4949 - Remove the tor_strpartition() function: its logic was confused,
4950 and it was only used for one thing that could be implemented far
4952 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
4953 and TorControl.py, as they use the old v0 controller protocol,
4954 and are obsoleted by TorFlow anyway.
4955 - Drop support for v1 rendezvous descriptors, since we never used
4956 them anyway, and the code has probably rotted by now. Based on
4957 patch from Karsten Loesing.
4958 - Stop allowing address masks that do not correspond to bit prefixes.
4959 We have warned about these for a really long time; now it's time
4960 to reject them. (Patch from croup.)
4961 - Remove an optimization in the AES counter-mode code that assumed
4962 that the counter never exceeded 2^68. When the counter can be set
4963 arbitrarily as an IV (as it is by Karsten's new hidden services
4964 code), this assumption no longer holds.
4965 - Disable the SETROUTERPURPOSE controller command: it is now
4969 Changes in version 0.1.2.19 - 2008-01-17
4970 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
4971 exit policy a little bit more conservative so it's safer to run an
4972 exit relay on a home system, and fixes a variety of smaller issues.
4975 - Exit policies now reject connections that are addressed to a
4976 relay's public (external) IP address too, unless
4977 ExitPolicyRejectPrivate is turned off. We do this because too
4978 many relays are running nearby to services that trust them based
4982 - When the clock jumps forward a lot, do not allow the bandwidth
4983 buckets to become negative. Fixes bug 544.
4984 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
4985 on every successful resolve. Reported by Mike Perry.
4986 - Purge old entries from the "rephist" database and the hidden
4987 service descriptor database even when DirPort is zero.
4988 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
4989 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
4990 crashing or mis-answering these requests.
4991 - When we decide to send a 503 response to a request for servers, do
4992 not then also send the server descriptors: this defeats the whole
4993 purpose. Fixes bug 539.
4996 - Changing the ExitPolicyRejectPrivate setting should cause us to
4997 rebuild our server descriptor.
4998 - Fix handling of hex nicknames when answering controller requests for
4999 networkstatus by name, or when deciding whether to warn about
5000 unknown routers in a config option. (Patch from mwenge.)
5001 - Fix a couple of hard-to-trigger autoconf problems that could result
5002 in really weird results on platforms whose sys/types.h files define
5003 nonstandard integer types.
5004 - Don't try to create the datadir when running --verify-config or
5005 --hash-password. Resolves bug 540.
5006 - If we were having problems getting a particular descriptor from the
5007 directory caches, and then we learned about a new descriptor for
5008 that router, we weren't resetting our failure count. Reported
5010 - Although we fixed bug 539 (where servers would send HTTP status 503
5011 responses _and_ send a body too), there are still servers out there
5012 that haven't upgraded. Therefore, make clients parse such bodies
5013 when they receive them.
5014 - Run correctly on systems where rlim_t is larger than unsigned long.
5015 This includes some 64-bit systems.
5016 - Run correctly on platforms (like some versions of OS X 10.5) where
5017 the real limit for number of open files is OPEN_FILES, not rlim_max
5018 from getrlimit(RLIMIT_NOFILES).
5019 - Avoid a spurious free on base64 failure.
5020 - Avoid segfaults on certain complex invocations of
5021 router_get_by_hexdigest().
5022 - Fix rare bug on REDIRECTSTREAM control command when called with no
5023 port set: it could erroneously report an error when none had
5027 Changes in version 0.1.2.18 - 2007-10-28
5028 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
5029 hidden service introduction that were causing huge delays, and a big
5030 bug that was causing some servers to disappear from the network status
5031 lists for a few hours each day.
5033 o Major bugfixes (crashes):
5034 - If a connection is shut down abruptly because of something that
5035 happened inside connection_flushed_some(), do not call
5036 connection_finished_flushing(). Should fix bug 451:
5037 "connection_stop_writing: Assertion conn->write_event failed"
5038 Bugfix on 0.1.2.7-alpha.
5039 - Fix possible segfaults in functions called from
5040 rend_process_relay_cell().
5042 o Major bugfixes (hidden services):
5043 - Hidden services were choosing introduction points uniquely by
5044 hexdigest, but when constructing the hidden service descriptor
5045 they merely wrote the (potentially ambiguous) nickname.
5046 - Clients now use the v2 intro format for hidden service
5047 connections: they specify their chosen rendezvous point by identity
5048 digest rather than by (potentially ambiguous) nickname. These
5049 changes could speed up hidden service connections dramatically.
5051 o Major bugfixes (other):
5052 - Stop publishing a new server descriptor just because we get a
5053 HUP signal. This led (in a roundabout way) to some servers getting
5054 dropped from the networkstatus lists for a few hours each day.
5055 - When looking for a circuit to cannibalize, consider family as well
5056 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
5057 circuit cannibalization).
5058 - When a router wasn't listed in a new networkstatus, we were leaving
5059 the flags for that router alone -- meaning it remained Named,
5060 Running, etc -- even though absence from the networkstatus means
5061 that it shouldn't be considered to exist at all anymore. Now we
5062 clear all the flags for routers that fall out of the networkstatus
5063 consensus. Fixes bug 529.
5066 - Don't try to access (or alter) the state file when running
5067 --list-fingerprint or --verify-config or --hash-password. Resolves
5069 - When generating information telling us how to extend to a given
5070 router, do not try to include the nickname if it is
5071 absent. Resolves bug 467.
5072 - Fix a user-triggerable segfault in expand_filename(). (There isn't
5073 a way to trigger this remotely.)
5074 - When sending a status event to the controller telling it that an
5075 OR address is reachable, set the port correctly. (Previously we
5076 were reporting the dir port.)
5077 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
5078 command. Bugfix on 0.1.2.17.
5079 - When loading bandwidth history, do not believe any information in
5080 the future. Fixes bug 434.
5081 - When loading entry guard information, do not believe any information
5083 - When we have our clock set far in the future and generate an
5084 onion key, then re-set our clock to be correct, we should not stop
5085 the onion key from getting rotated.
5086 - On some platforms, accept() can return a broken address. Detect
5087 this more quietly, and deal accordingly. Fixes bug 483.
5088 - It's not actually an error to find a non-pending entry in the DNS
5089 cache when canceling a pending resolve. Don't log unless stuff
5090 is fishy. Resolves bug 463.
5091 - Don't reset trusted dir server list when we set a configuration
5092 option. Patch from Robert Hogan.
5095 Changes in version 0.1.2.17 - 2007-08-30
5096 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
5097 X bundles. Vidalia 0.0.14 makes authentication required for the
5098 ControlPort in the default configuration, which addresses important
5099 security risks. Everybody who uses Vidalia (or another controller)
5102 In addition, this Tor update fixes major load balancing problems with
5103 path selection, which should speed things up a lot once many people
5106 o Major bugfixes (security):
5107 - We removed support for the old (v0) control protocol. It has been
5108 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
5109 become more of a headache than it's worth.
5111 o Major bugfixes (load balancing):
5112 - When choosing nodes for non-guard positions, weight guards
5113 proportionally less, since they already have enough load. Patch
5115 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
5116 will allow fast Tor servers to get more attention.
5117 - When we're upgrading from an old Tor version, forget our current
5118 guards and pick new ones according to the new weightings. These
5119 three load balancing patches could raise effective network capacity
5120 by a factor of four. Thanks to Mike Perry for measurements.
5122 o Major bugfixes (stream expiration):
5123 - Expire not-yet-successful application streams in all cases if
5124 they've been around longer than SocksTimeout. Right now there are
5125 some cases where the stream will live forever, demanding a new
5126 circuit every 15 seconds. Fixes bug 454; reported by lodger.
5128 o Minor features (controller):
5129 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
5130 is valid before any authentication has been received. It tells
5131 a controller what kind of authentication is expected, and what
5132 protocol is spoken. Implements proposal 119.
5134 o Minor bugfixes (performance):
5135 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
5136 greatly speeding up loading cached-routers from disk on startup.
5137 - Disable sentinel-based debugging for buffer code: we squashed all
5138 the bugs that this was supposed to detect a long time ago, and now
5139 its only effect is to change our buffer sizes from nice powers of
5140 two (which platform mallocs tend to like) to values slightly over
5141 powers of two (which make some platform mallocs sad).
5143 o Minor bugfixes (misc):
5144 - If exit bandwidth ever exceeds one third of total bandwidth, then
5145 use the correct formula to weight exit nodes when choosing paths.
5146 Based on patch from Mike Perry.
5147 - Choose perfectly fairly among routers when choosing by bandwidth and
5148 weighting by fraction of bandwidth provided by exits. Previously, we
5149 would choose with only approximate fairness, and correct ourselves
5150 if we ran off the end of the list.
5151 - If we require CookieAuthentication but we fail to write the
5152 cookie file, we would warn but not exit, and end up in a state
5153 where no controller could authenticate. Now we exit.
5154 - If we require CookieAuthentication, stop generating a new cookie
5155 every time we change any piece of our config.
5156 - Refuse to start with certain directory authority keys, and
5157 encourage people using them to stop.
5158 - Terminate multi-line control events properly. Original patch
5160 - Fix a minor memory leak when we fail to find enough suitable
5161 servers to choose a circuit.
5162 - Stop leaking part of the descriptor when we run into a particularly
5163 unparseable piece of it.
5166 Changes in version 0.1.2.16 - 2007-08-01
5167 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
5168 remote attacker in certain situations to rewrite the user's torrc
5169 configuration file. This can completely compromise anonymity of users
5170 in most configurations, including those running the Vidalia bundles,
5171 TorK, etc. Or worse.
5173 o Major security fixes:
5174 - Close immediately after missing authentication on control port;
5175 do not allow multiple authentication attempts.
5178 Changes in version 0.1.2.15 - 2007-07-17
5179 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
5180 problems, fixes compilation on BSD, and fixes a variety of other
5181 bugs. Everybody should upgrade.
5183 o Major bugfixes (compilation):
5184 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
5186 o Major bugfixes (crashes):
5187 - Try even harder not to dereference the first character after
5188 an mmap(). Reported by lodger.
5189 - Fix a crash bug in directory authorities when we re-number the
5190 routerlist while inserting a new router.
5191 - When the cached-routers file is an even multiple of the page size,
5192 don't run off the end and crash. (Fixes bug 455; based on idea
5194 - Fix eventdns.c behavior on Solaris: It is critical to include
5195 orconfig.h _before_ sys/types.h, so that we can get the expected
5196 definition of _FILE_OFFSET_BITS.
5198 o Major bugfixes (security):
5199 - Fix a possible buffer overrun when using BSD natd support. Bug
5201 - When sending destroy cells from a circuit's origin, don't include
5202 the reason for tearing down the circuit. The spec says we didn't,
5203 and now we actually don't. Reported by lodger.
5204 - Keep streamids from different exits on a circuit separate. This
5205 bug may have allowed other routers on a given circuit to inject
5206 cells into streams. Reported by lodger; fixes bug 446.
5207 - If there's a never-before-connected-to guard node in our list,
5208 never choose any guards past it. This way we don't expand our
5209 guard list unless we need to.
5211 o Minor bugfixes (guard nodes):
5212 - Weight guard selection by bandwidth, so that low-bandwidth nodes
5213 don't get overused as guards.
5215 o Minor bugfixes (directory):
5216 - Correctly count the number of authorities that recommend each
5217 version. Previously, we were under-counting by 1.
5218 - Fix a potential crash bug when we load many server descriptors at
5219 once and some of them make others of them obsolete. Fixes bug 458.
5221 o Minor bugfixes (hidden services):
5222 - Stop tearing down the whole circuit when the user asks for a
5223 connection to a port that the hidden service didn't configure.
5226 o Minor bugfixes (misc):
5227 - On Windows, we were preventing other processes from reading
5228 cached-routers while Tor was running. Reported by janbar.
5229 - Fix a possible (but very unlikely) bug in picking routers by
5230 bandwidth. Add a log message to confirm that it is in fact
5231 unlikely. Patch from lodger.
5232 - Backport a couple of memory leak fixes.
5233 - Backport miscellaneous cosmetic bugfixes.
5236 Changes in version 0.1.2.14 - 2007-05-25
5237 Tor 0.1.2.14 changes the addresses of two directory authorities (this
5238 change especially affects those who serve or use hidden services),
5239 and fixes several other crash- and security-related bugs.
5241 o Directory authority changes:
5242 - Two directory authorities (moria1 and moria2) just moved to new
5243 IP addresses. This change will particularly affect those who serve
5244 or use hidden services.
5246 o Major bugfixes (crashes):
5247 - If a directory server runs out of space in the connection table
5248 as it's processing a begin_dir request, it will free the exit stream
5249 but leave it attached to the circuit, leading to unpredictable
5250 behavior. (Reported by seeess, fixes bug 425.)
5251 - Fix a bug in dirserv_remove_invalid() that would cause authorities
5252 to corrupt memory under some really unlikely scenarios.
5253 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
5254 - Avoid segfaults when reading from mmaped descriptor file. (Reported
5257 o Major bugfixes (security):
5258 - When choosing an entry guard for a circuit, avoid using guards
5259 that are in the same family as the chosen exit -- not just guards
5260 that are exactly the chosen exit. (Reported by lodger.)
5262 o Major bugfixes (resource management):
5263 - If a directory authority is down, skip it when deciding where to get
5264 networkstatus objects or descriptors. Otherwise we keep asking
5265 every 10 seconds forever. Fixes bug 384.
5266 - Count it as a failure if we fetch a valid network-status but we
5267 don't want to keep it. Otherwise we'll keep fetching it and keep
5268 not wanting to keep it. Fixes part of bug 422.
5269 - If all of our dirservers have given us bad or no networkstatuses
5270 lately, then stop hammering them once per minute even when we
5271 think they're failed. Fixes another part of bug 422.
5274 - Actually set the purpose correctly for descriptors inserted with
5276 - When we have k non-v2 authorities in our DirServer config,
5277 we ignored the last k authorities in the list when updating our
5279 - Correctly back-off from requesting router descriptors that we are
5280 having a hard time downloading.
5281 - Read resolv.conf files correctly on platforms where read() returns
5282 partial results on small file reads.
5283 - Don't rebuild the entire router store every time we get 32K of
5284 routers: rebuild it when the journal gets very large, or when
5285 the gaps in the store get very large.
5288 - When routers publish SVN revisions in their router descriptors,
5289 authorities now include those versions correctly in networkstatus
5291 - Warn when using a version of libevent before 1.3b to run a server on
5292 OSX or BSD: these versions interact badly with userspace threads.
5295 Changes in version 0.1.2.13 - 2007-04-24
5296 This release features some major anonymity fixes, such as safer path
5297 selection; better client performance; faster bootstrapping, better
5298 address detection, and better DNS support for servers; write limiting as
5299 well as read limiting to make servers easier to run; and a huge pile of
5300 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
5302 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
5303 of the Freenode IRC network, remembering his patience and vision for
5304 free speech on the Internet.
5306 o Major features, client performance:
5307 - Weight directory requests by advertised bandwidth. Now we can
5308 let servers enable write limiting but still allow most clients to
5309 succeed at their directory requests. (We still ignore weights when
5310 choosing a directory authority; I hope this is a feature.)
5311 - Stop overloading exit nodes -- avoid choosing them for entry or
5312 middle hops when the total bandwidth available from non-exit nodes
5313 is much higher than the total bandwidth available from exit nodes.
5314 - Rather than waiting a fixed amount of time between retrying
5315 application connections, we wait only 10 seconds for the first,
5316 10 seconds for the second, and 15 seconds for each retry after
5317 that. Hopefully this will improve the expected user experience.
5318 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
5319 to open a stream fails; now we do in more cases. This should
5320 make clients able to find a good exit faster in some cases, since
5321 unhandleable requests will now get an error rather than timing out.
5323 o Major features, client functionality:
5324 - Implement BEGIN_DIR cells, so we can connect to a directory
5325 server via TLS to do encrypted directory requests rather than
5326 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
5327 config options if you like. For now, this feature only works if
5328 you already have a descriptor for the destination dirserver.
5329 - Add support for transparent application connections: this basically
5330 bundles the functionality of trans-proxy-tor into the Tor
5331 mainline. Now hosts with compliant pf/netfilter implementations
5332 can redirect TCP connections straight to Tor without diverting
5333 through SOCKS. (Based on patch from tup.)
5334 - Add support for using natd; this allows FreeBSDs earlier than
5335 5.1.2 to have ipfw send connections through Tor without using
5336 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
5338 o Major features, servers:
5339 - Setting up a dyndns name for your server is now optional: servers
5340 with no hostname or IP address will learn their IP address by
5341 asking the directory authorities. This code only kicks in when you
5342 would normally have exited with a "no address" error. Nothing's
5343 authenticated, so use with care.
5344 - Directory servers now spool server descriptors, v1 directories,
5345 and v2 networkstatus objects to buffers as needed rather than en
5346 masse. They also mmap the cached-routers files. These steps save
5348 - Stop requiring clients to have well-formed certificates, and stop
5349 checking nicknames in certificates. (Clients have certificates so
5350 that they can look like Tor servers, but in the future we might want
5351 to allow them to look like regular TLS clients instead. Nicknames
5352 in certificates serve no purpose other than making our protocol
5353 easier to recognize on the wire.) Implements proposal 106.
5355 o Improvements on DNS support:
5356 - Add "eventdns" asynchronous dns library originally based on code
5357 from Adam Langley. Now we can discard the old rickety dnsworker
5358 concept, and support a wider variety of DNS functions. Allows
5359 multithreaded builds on NetBSD and OpenBSD again.
5360 - Add server-side support for "reverse" DNS lookups (using PTR
5361 records so clients can determine the canonical hostname for a given
5362 IPv4 address). Only supported by servers using eventdns; servers
5363 now announce in their descriptors if they don't support eventdns.
5364 - Workaround for name servers (like Earthlink's) that hijack failing
5365 DNS requests and replace the no-such-server answer with a "helpful"
5366 redirect to an advertising-driven search portal. Also work around
5367 DNS hijackers who "helpfully" decline to hijack known-invalid
5368 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
5369 lets you turn it off.
5370 - Servers now check for the case when common DNS requests are going to
5371 wildcarded addresses (i.e. all getting the same answer), and change
5372 their exit policy to reject *:* if it's happening.
5373 - When asked to resolve a hostname, don't use non-exit servers unless
5374 requested to do so. This allows servers with broken DNS to be
5375 useful to the network.
5376 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
5377 useless IPv6 DNS resolves.
5378 - Specify and implement client-side SOCKS5 interface for reverse DNS
5379 lookups (see doc/socks-extensions.txt). Also cache them.
5380 - When we change nameservers or IP addresses, reset and re-launch
5381 our tests for DNS hijacking.
5383 o Improvements on reachability testing:
5384 - Servers send out a burst of long-range padding cells once they've
5385 established that they're reachable. Spread them over 4 circuits,
5386 so hopefully a few will be fast. This exercises bandwidth and
5387 bootstraps them into the directory more quickly.
5388 - When we find our DirPort to be reachable, publish a new descriptor
5389 so we'll tell the world (reported by pnx).
5390 - Directory authorities now only decide that routers are reachable
5391 if their identity keys are as expected.
5392 - Do DirPort reachability tests less often, since a single test
5393 chews through many circuits before giving up.
5394 - Avoid some false positives during reachability testing: don't try
5395 to test via a server that's on the same /24 network as us.
5396 - Start publishing one minute or so after we find our ORPort
5397 to be reachable. This will help reduce the number of descriptors
5398 we have for ourselves floating around, since it's quite likely
5399 other things (e.g. DirPort) will change during that minute too.
5400 - Routers no longer try to rebuild long-term connections to directory
5401 authorities, and directory authorities no longer try to rebuild
5402 long-term connections to all servers. We still don't hang up
5403 connections in these two cases though -- we need to look at it
5404 more carefully to avoid flapping, and we likely need to wait til
5405 0.1.1.x is obsolete.
5407 o Improvements on rate limiting:
5408 - Enable write limiting as well as read limiting. Now we sacrifice
5409 capacity if we're pushing out lots of directory traffic, rather
5410 than overrunning the user's intended bandwidth limits.
5411 - Include TLS overhead when counting bandwidth usage; previously, we
5412 would count only the bytes sent over TLS, but not the bytes used
5414 - Servers decline directory requests much more aggressively when
5415 they're low on bandwidth. Otherwise they end up queueing more and
5416 more directory responses, which can't be good for latency.
5417 - But never refuse directory requests from local addresses.
5418 - Be willing to read or write on local connections (e.g. controller
5419 connections) even when the global rate limiting buckets are empty.
5420 - Flush local controller connection buffers periodically as we're
5421 writing to them, so we avoid queueing 4+ megabytes of data before
5423 - Revise and clean up the torrc.sample that we ship with; add
5424 a section for BandwidthRate and BandwidthBurst.
5426 o Major features, NT services:
5427 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
5428 command-line flag so that admins can override the default by saying
5429 "tor --service install --user "SomeUser"". This will not affect
5430 existing installed services. Also, warn the user that the service
5431 will look for its configuration file in the service user's
5432 %appdata% directory. (We can't do the "hardwire the user's appdata
5433 directory" trick any more, since we may not have read access to that
5435 - Support running the Tor service with a torrc not in the same
5436 directory as tor.exe and default to using the torrc located in
5437 the %appdata%\Tor\ of the user who installed the service. Patch
5439 - Add an --ignore-missing-torrc command-line option so that we can
5440 get the "use sensible defaults if the configuration file doesn't
5441 exist" behavior even when specifying a torrc location on the
5443 - When stopping an NT service, wait up to 10 sec for it to actually
5444 stop. (Patch from Matt Edman; resolves bug 295.)
5446 o Directory authority improvements:
5447 - Stop letting hibernating or obsolete servers affect uptime and
5449 - Stop listing hibernating servers in the v1 directory.
5450 - Authorities no longer recommend exits as guards if this would shift
5451 too much load to the exit nodes.
5452 - Authorities now specify server versions in networkstatus. This adds
5453 about 2% to the size of compressed networkstatus docs, and allows
5454 clients to tell which servers support BEGIN_DIR and which don't.
5455 The implementation is forward-compatible with a proposed future
5456 protocol version scheme not tied to Tor versions.
5457 - DirServer configuration lines now have an orport= option so
5458 clients can open encrypted tunnels to the authorities without
5459 having downloaded their descriptors yet. Enabled for moria1,
5460 moria2, tor26, and lefkada now in the default configuration.
5461 - Add a BadDirectory flag to network status docs so that authorities
5462 can (eventually) tell clients about caches they believe to be
5463 broken. Not used yet.
5464 - Allow authorities to list nodes as bad exits in their
5465 approved-routers file by fingerprint or by address. If most
5466 authorities set a BadExit flag for a server, clients don't think
5467 of it as a general-purpose exit. Clients only consider authorities
5468 that advertise themselves as listing bad exits.
5469 - Patch from Steve Hildrey: Generate network status correctly on
5470 non-versioning dirservers.
5471 - Have directory authorities allow larger amounts of drift in uptime
5472 without replacing the server descriptor: previously, a server that
5473 restarted every 30 minutes could have 48 "interesting" descriptors
5475 - Reserve the nickname "Unnamed" for routers that can't pick
5476 a hostname: any router can call itself Unnamed; directory
5477 authorities will never allocate Unnamed to any particular router;
5478 clients won't believe that any router is the canonical Unnamed.
5480 o Directory mirrors and clients:
5481 - Discard any v1 directory info that's over 1 month old (for
5482 directories) or over 1 week old (for running-routers lists).
5483 - Clients track responses with status 503 from dirservers. After a
5484 dirserver has given us a 503, we try not to use it until an hour has
5485 gone by, or until we have no dirservers that haven't given us a 503.
5486 - When we get a 503 from a directory, and we're not a server, we no
5487 longer count the failure against the total number of failures
5488 allowed for the object we're trying to download.
5489 - Prepare for servers to publish descriptors less often: never
5490 discard a descriptor simply for being too old until either it is
5491 recommended by no authorities, or until we get a better one for
5492 the same router. Make caches consider retaining old recommended
5493 routers for even longer.
5494 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
5495 headers for content, so that we can work better in the presence of
5496 caching HTTP proxies.
5497 - Stop fetching descriptors if you're not a dir mirror and you
5498 haven't tried to establish any circuits lately. (This currently
5499 causes some dangerous behavior, because when you start up again
5500 you'll use your ancient server descriptors.)
5502 o Major fixes, crashes:
5503 - Stop crashing when the controller asks us to resetconf more than
5504 one config option at once. (Vidalia 0.0.11 does this.)
5505 - Fix a longstanding obscure crash bug that could occur when we run
5506 out of DNS worker processes, if we're not using eventdns. (Resolves
5508 - Fix an assert that could trigger if a controller quickly set then
5509 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
5510 - Avoid crash when telling controller about stream-status and a
5512 - Avoid sending junk to controllers or segfaulting when a controller
5513 uses EVENT_NEW_DESC with verbose nicknames.
5514 - Stop triggering asserts if the controller tries to extend hidden
5515 service circuits (reported by mwenge).
5516 - If we start a server with ClientOnly 1, then set ClientOnly to 0
5517 and hup, stop triggering an assert based on an empty onion_key.
5518 - Mask out all signals in sub-threads; only the libevent signal
5519 handler should be processing them. This should prevent some crashes
5520 on some machines using pthreads. (Patch from coderman.)
5521 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
5523 o Major fixes, anonymity/security:
5524 - Automatically avoid picking more than one node from the same
5525 /16 network when constructing a circuit. Add an
5526 "EnforceDistinctSubnets" option to let people disable it if they
5527 want to operate private test networks on a single subnet.
5528 - When generating bandwidth history, round down to the nearest
5529 1k. When storing accounting data, round up to the nearest 1k.
5530 - When we're running as a server, remember when we last rotated onion
5531 keys, so that we will rotate keys once they're a week old even if
5532 we never stay up for a week ourselves.
5533 - If a client asked for a server by name, and there's a named server
5534 in our network-status but we don't have its descriptor yet, we
5535 could return an unnamed server instead.
5536 - Reject (most) attempts to use Tor circuits with length one. (If
5537 many people start using Tor as a one-hop proxy, exit nodes become
5538 a more attractive target for compromise.)
5539 - Just because your DirPort is open doesn't mean people should be
5540 able to remotely teach you about hidden service descriptors. Now
5541 only accept rendezvous posts if you've got HSAuthoritativeDir set.
5542 - Fix a potential race condition in the rpm installer. Found by
5544 - Do not log IPs with TLS failures for incoming TLS
5545 connections. (Fixes bug 382.)
5547 o Major fixes, other:
5548 - If our system clock jumps back in time, don't publish a negative
5549 uptime in the descriptor.
5550 - When we start during an accounting interval before it's time to wake
5551 up, remember to wake up at the correct time. (May fix bug 342.)
5552 - Previously, we would cache up to 16 old networkstatus documents
5553 indefinitely, if they came from nontrusted authorities. Now we
5554 discard them if they are more than 10 days old.
5555 - When we have a state file we cannot parse, tell the user and
5556 move it aside. Now we avoid situations where the user starts
5557 Tor in 1904, Tor writes a state file with that timestamp in it,
5558 the user fixes her clock, and Tor refuses to start.
5559 - Publish a new descriptor after we hup/reload. This is important
5560 if our config has changed such that we'll want to start advertising
5561 our DirPort now, etc.
5562 - If we are using an exit enclave and we can't connect, e.g. because
5563 its webserver is misconfigured to not listen on localhost, then
5564 back off and try connecting from somewhere else before we fail.
5566 o New config options or behaviors:
5567 - When EntryNodes are configured, rebuild the guard list to contain,
5568 in order: the EntryNodes that were guards before; the rest of the
5569 EntryNodes; the nodes that were guards before.
5570 - Do not warn when individual nodes in the configuration's EntryNodes,
5571 ExitNodes, etc are down: warn only when all possible nodes
5572 are down. (Fixes bug 348.)
5573 - Put a lower-bound on MaxAdvertisedBandwidth.
5574 - Start using the state file to store bandwidth accounting data:
5575 the bw_accounting file is now obsolete. We'll keep generating it
5576 for a while for people who are still using 0.1.2.4-alpha.
5577 - Try to batch changes to the state file so that we do as few
5578 disk writes as possible while still storing important things in
5580 - The state file and the bw_accounting file get saved less often when
5581 the AvoidDiskWrites config option is set.
5582 - Make PIDFile work on Windows.
5583 - Add internal descriptions for a bunch of configuration options:
5584 accessible via controller interface and in comments in saved
5586 - Reject *:563 (NNTPS) in the default exit policy. We already reject
5587 NNTP by default, so this seems like a sensible addition.
5588 - Clients now reject hostnames with invalid characters. This should
5589 avoid some inadvertent info leaks. Add an option
5590 AllowNonRFC953Hostnames to disable this behavior, in case somebody
5591 is running a private network with hosts called @, !, and #.
5592 - Check for addresses with invalid characters at the exit as well,
5593 and warn less verbosely when they fail. You can override this by
5594 setting ServerDNSAllowNonRFC953Addresses to 1.
5595 - Remove some options that have been deprecated since at least
5596 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
5597 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
5598 to set log options. Mark PathlenCoinWeight as obsolete.
5599 - Stop accepting certain malformed ports in configured exit policies.
5600 - When the user uses bad syntax in the Log config line, stop
5601 suggesting other bad syntax as a replacement.
5602 - Add new config option "ResolvConf" to let the server operator
5603 choose an alternate resolve.conf file when using eventdns.
5604 - If one of our entry guards is on the ExcludeNodes list, or the
5605 directory authorities don't think it's a good guard, treat it as
5606 if it were unlisted: stop using it as a guard, and throw it off
5607 the guards list if it stays that way for a long time.
5608 - Allow directory authorities to be marked separately as authorities
5609 for the v1 directory protocol, the v2 directory protocol, and
5610 as hidden service directories, to make it easier to retire old
5611 authorities. V1 authorities should set "HSAuthoritativeDir 1"
5612 to continue being hidden service authorities too.
5613 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
5614 - Make TrackExitHosts case-insensitive, and fix the behavior of
5615 ".suffix" TrackExitHosts items to avoid matching in the middle of
5617 - New DirPort behavior: if you have your dirport set, you download
5618 descriptors aggressively like a directory mirror, whether or not
5622 - Create a new file ReleaseNotes which was the old ChangeLog. The
5623 new ChangeLog file now includes the notes for all development
5625 - Add a new address-spec.txt document to describe our special-case
5626 addresses: .exit, .onion, and .noconnnect.
5627 - Fork the v1 directory protocol into its own spec document,
5628 and mark dir-spec.txt as the currently correct (v2) spec.
5630 o Packaging, porting, and contrib
5631 - "tor --verify-config" now exits with -1(255) or 0 depending on
5632 whether the config options are bad or good.
5633 - The Debian package now uses --verify-config when (re)starting,
5634 to distinguish configuration errors from other errors.
5635 - Adapt a patch from goodell to let the contrib/exitlist script
5636 take arguments rather than require direct editing.
5637 - Prevent the contrib/exitlist script from printing the same
5638 result more than once.
5639 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
5640 - In the hidden service example in torrc.sample, stop recommending
5641 esoteric and discouraged hidden service options.
5642 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
5643 values before failing, and always enables eventdns.
5644 - Try to detect Windows correctly when cross-compiling.
5645 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
5646 Try to fix this in configure.in by checking for most functions
5647 before we check for libevent.
5648 - Update RPMs to require libevent 1.2.
5649 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
5650 or later. Log when we are doing this, so we can diagnose it when
5651 it fails. (Also, recommend libevent 1.1b for kqueue and
5652 win32 methods; deprecate libevent 1.0b harder; make libevent
5653 recommendation system saner.)
5654 - Build with recent (1.3+) libevents on platforms that do not
5655 define the nonstandard types "u_int8_t" and friends.
5656 - Remove architecture from OS X builds. The official builds are
5657 now universal binaries.
5658 - Run correctly on OS X platforms with case-sensitive filesystems.
5659 - Correctly set maximum connection limit on Cygwin. (This time
5661 - Start compiling on MinGW on Windows (patches from Mike Chiussi
5663 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
5664 - Finally fix the openssl warnings from newer gccs that believe that
5665 ignoring a return value is okay, but casting a return value and
5666 then ignoring it is a sign of madness.
5667 - On architectures where sizeof(int)>4, still clamp declarable
5668 bandwidth to INT32_MAX.
5670 o Minor features, controller:
5671 - Warn the user when an application uses the obsolete binary v0
5672 control protocol. We're planning to remove support for it during
5673 the next development series, so it's good to give people some
5675 - Add STREAM_BW events to report per-entry-stream bandwidth
5676 use. (Patch from Robert Hogan.)
5677 - Rate-limit SIGNEWNYM signals in response to controllers that
5678 impolitely generate them for every single stream. (Patch from
5679 mwenge; closes bug 394.)
5680 - Add a REMAP status to stream events to note that a stream's
5681 address has changed because of a cached address or a MapAddress
5683 - Make REMAP stream events have a SOURCE (cache or exit), and
5684 make them generated in every case where we get a successful
5685 connected or resolved cell.
5686 - Track reasons for OR connection failure; make these reasons
5687 available via the controller interface. (Patch from Mike Perry.)
5688 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
5689 can learn when clients are sending malformed hostnames to Tor.
5690 - Specify and implement some of the controller status events.
5691 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
5692 - Reimplement GETINFO so that info/names stays in sync with the
5694 - Implement "GETINFO fingerprint".
5695 - Implement "SETEVENTS GUARD" so controllers can get updates on
5696 entry guard status as it changes.
5697 - Make all connections to addresses of the form ".noconnect"
5698 immediately get closed. This lets application/controller combos
5699 successfully test whether they're talking to the same Tor by
5700 watching for STREAM events.
5701 - Add a REASON field to CIRC events; for backward compatibility, this
5702 field is sent only to controllers that have enabled the extended
5703 event format. Also, add additional reason codes to explain why
5704 a given circuit has been destroyed or truncated. (Patches from
5706 - Add a REMOTE_REASON field to extended CIRC events to tell the
5707 controller why a remote OR told us to close a circuit.
5708 - Stream events also now have REASON and REMOTE_REASON fields,
5709 working much like those for circuit events.
5710 - There's now a GETINFO ns/... field so that controllers can ask Tor
5711 about the current status of a router.
5712 - A new event type "NS" to inform a controller when our opinion of
5713 a router's status has changed.
5714 - Add a GETINFO events/names and GETINFO features/names so controllers
5715 can tell which events and features are supported.
5716 - A new CLEARDNSCACHE signal to allow controllers to clear the
5717 client-side DNS cache without expiring circuits.
5718 - Fix CIRC controller events so that controllers can learn the
5719 identity digests of non-Named servers used in circuit paths.
5720 - Let controllers ask for more useful identifiers for servers. Instead
5721 of learning identity digests for un-Named servers and nicknames
5722 for Named servers, the new identifiers include digest, nickname,
5723 and indication of Named status. Off by default; see control-spec.txt
5724 for more information.
5725 - Add a "getinfo address" controller command so it can display Tor's
5726 best guess to the user.
5727 - New controller event to alert the controller when our server
5728 descriptor has changed.
5729 - Give more meaningful errors on controller authentication failure.
5730 - Export the default exit policy via the control port, so controllers
5731 don't need to guess what it is / will be later.
5733 o Minor bugfixes, controller:
5734 - When creating a circuit via the controller, send a 'launched'
5735 event when we're done, so we follow the spec better.
5736 - Correct the control spec to match how the code actually responds
5737 to 'getinfo addr-mappings/*'. Reported by daejees.
5738 - The control spec described a GUARDS event, but the code
5739 implemented a GUARD event. Standardize on GUARD, but let people
5740 ask for GUARDS too. Reported by daejees.
5741 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
5742 clear the corresponding on_circuit variable, and remember later
5743 that we don't need to send a redundant CLOSED event. (Resolves part
5745 - Report events where a resolve succeeded or where we got a socks
5746 protocol error correctly, rather than calling both of them
5748 - Change reported stream target addresses to IP consistently when
5749 we finally get the IP from an exit node.
5750 - Send log messages to the controller even if they happen to be very
5752 - Flush ERR-level controller status events just like we currently
5753 flush ERR-level log events, so that a Tor shutdown doesn't prevent
5754 the controller from learning about current events.
5755 - Report the circuit number correctly in STREAM CLOSED events. Bug
5756 reported by Mike Perry.
5757 - Do not report bizarre values for results of accounting GETINFOs
5758 when the last second's write or read exceeds the allotted bandwidth.
5759 - Report "unrecognized key" rather than an empty string when the
5760 controller tries to fetch a networkstatus that doesn't exist.
5761 - When the controller does a "GETINFO network-status", tell it
5762 about even those routers whose descriptors are very old, and use
5763 long nicknames where appropriate.
5764 - Fix handling of verbose nicknames with ORCONN controller events:
5765 make them show up exactly when requested, rather than exactly when
5767 - Controller signals now work on non-Unix platforms that don't define
5768 SIGUSR1 and SIGUSR2 the way we expect.
5769 - Respond to SIGNAL command before we execute the signal, in case
5770 the signal shuts us down. Suggested by Karsten Loesing.
5771 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
5773 o Minor features, code performance:
5774 - Major performance improvement on inserting descriptors: change
5775 algorithm from O(n^2) to O(n).
5776 - Do not rotate onion key immediately after setting it for the first
5778 - Call router_have_min_dir_info half as often. (This is showing up in
5779 some profiles, but not others.)
5780 - When using GCC, make log_debug never get called at all, and its
5781 arguments never get evaluated, when no debug logs are configured.
5782 (This is showing up in some profiles, but not others.)
5783 - Statistics dumped by -USR2 now include a breakdown of public key
5784 operations, for profiling.
5785 - Make the common memory allocation path faster on machines where
5786 malloc(0) returns a pointer.
5787 - Split circuit_t into origin_circuit_t and or_circuit_t, and
5788 split connection_t into edge, or, dir, control, and base structs.
5789 These will save quite a bit of memory on busy servers, and they'll
5790 also help us track down bugs in the code and bugs in the spec.
5791 - Use OpenSSL's AES implementation on platforms where it's faster.
5792 This could save us as much as 10% CPU usage.
5794 o Minor features, descriptors and descriptor handling:
5795 - Avoid duplicate entries on MyFamily line in server descriptor.
5796 - When Tor receives a router descriptor that it asked for, but
5797 no longer wants (because it has received fresh networkstatuses
5798 in the meantime), do not warn the user. Cache the descriptor if
5799 we're a cache; drop it if we aren't.
5800 - Servers no longer ever list themselves in their "family" line,
5801 even if configured to do so. This makes it easier to configure
5802 family lists conveniently.
5804 o Minor fixes, confusing/misleading log messages:
5805 - Display correct results when reporting which versions are
5806 recommended, and how recommended they are. (Resolves bug 383.)
5807 - Inform the server operator when we decide not to advertise a
5808 DirPort due to AccountingMax enabled or a low BandwidthRate.
5809 - Only include function names in log messages for info/debug messages.
5810 For notice/warn/err, the content of the message should be clear on
5811 its own, and printing the function name only confuses users.
5812 - Remove even more protocol-related warnings from Tor server logs,
5813 such as bad TLS handshakes and malformed begin cells.
5814 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
5815 when the IP address is mapped through MapAddress to a hostname.
5816 - Fix misleading log messages: an entry guard that is "unlisted",
5817 as well as not known to be "down" (because we've never heard
5818 of it), is not therefore "up".
5820 o Minor fixes, old/obsolete behavior:
5821 - Start assuming we can use a create_fast cell if we don't know
5822 what version a router is running.
5823 - We no longer look for identity and onion keys in "identity.key" and
5824 "onion.key" -- these were replaced by secret_id_key and
5825 secret_onion_key in 0.0.8pre1.
5826 - We no longer require unrecognized directory entries to be
5828 - Drop compatibility with obsolete Tors that permit create cells
5829 to have the wrong circ_id_type.
5830 - Remove code to special-case "-cvs" ending, since it has not
5831 actually mattered since 0.0.9.
5832 - Don't re-write the fingerprint file every restart, unless it has
5835 o Minor fixes, misc client-side behavior:
5836 - Always remove expired routers and networkstatus docs before checking
5837 whether we have enough information to build circuits. (Fixes
5839 - When computing clock skew from directory HTTP headers, consider what
5840 time it was when we finished asking for the directory, not what
5842 - Make our socks5 handling more robust to broken socks clients:
5843 throw out everything waiting on the buffer in between socks
5844 handshake phases, since they can't possibly (so the theory
5845 goes) have predicted what we plan to respond to them.
5846 - Expire socks connections if they spend too long waiting for the
5847 handshake to finish. Previously we would let them sit around for
5848 days, if the connecting application didn't close them either.
5849 - And if the socks handshake hasn't started, don't send a
5850 "DNS resolve socks failed" handshake reply; just close it.
5851 - If the user asks to use invalid exit nodes, be willing to use
5853 - Track unreachable entry guards correctly: don't conflate
5854 'unreachable by us right now' with 'listed as down by the directory
5855 authorities'. With the old code, if a guard was unreachable by us
5856 but listed as running, it would clog our guard list forever.
5857 - Behave correctly in case we ever have a network with more than
5858 2GB/s total advertised capacity.
5859 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
5860 - Fix a memory leak when we ask for "all" networkstatuses and we
5861 get one we don't recognize.
5864 Changes in version 0.1.1.26 - 2006-12-14
5865 o Security bugfixes:
5866 - Stop sending the HttpProxyAuthenticator string to directory
5867 servers when directory connections are tunnelled through Tor.
5868 - Clients no longer store bandwidth history in the state file.
5869 - Do not log introduction points for hidden services if SafeLogging
5873 - Fix an assert failure when a directory authority sets
5874 AuthDirRejectUnlisted and then receives a descriptor from an
5875 unlisted router (reported by seeess).
5878 Changes in version 0.1.1.25 - 2006-11-04
5880 - When a client asks us to resolve (rather than connect to)
5881 an address, and we have a cached answer, give them the cached
5882 answer. Previously, we would give them no answer at all.
5883 - We were building exactly the wrong circuits when we predict
5884 hidden service requirements, meaning Tor would have to build all
5885 its circuits on demand.
5886 - If none of our live entry guards have a high uptime, but we
5887 require a guard with a high uptime, try adding a new guard before
5888 we give up on the requirement. This patch should make long-lived
5889 connections more stable on average.
5890 - When testing reachability of our DirPort, don't launch new
5891 tests when there's already one in progress -- unreachable
5892 servers were stacking up dozens of testing streams.
5894 o Security bugfixes:
5895 - When the user sends a NEWNYM signal, clear the client-side DNS
5896 cache too. Otherwise we continue to act on previous information.
5899 - Avoid a memory corruption bug when creating a hash table for
5901 - Avoid possibility of controller-triggered crash when misusing
5902 certain commands from a v0 controller on platforms that do not
5903 handle printf("%s",NULL) gracefully.
5904 - Avoid infinite loop on unexpected controller input.
5905 - Don't log spurious warnings when we see a circuit close reason we
5906 don't recognize; it's probably just from a newer version of Tor.
5907 - Add Vidalia to the OS X uninstaller script, so when we uninstall
5908 Tor/Privoxy we also uninstall Vidalia.
5911 Changes in version 0.1.1.24 - 2006-09-29
5913 - Allow really slow clients to not hang up five minutes into their
5914 directory downloads (suggested by Adam J. Richter).
5915 - Fix major performance regression from 0.1.0.x: instead of checking
5916 whether we have enough directory information every time we want to
5917 do something, only check when the directory information has changed.
5918 This should improve client CPU usage by 25-50%.
5919 - Don't crash if, after a server has been running for a while,
5920 it can't resolve its hostname.
5921 - When a client asks us to resolve (not connect to) an address,
5922 and we have a cached answer, give them the cached answer.
5923 Previously, we would give them no answer at all.
5926 - Allow Tor to start when RunAsDaemon is set but no logs are set.
5927 - Don't crash when the controller receives a third argument to an
5928 "extendcircuit" request.
5929 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
5930 response; fix error code when "getinfo dir/status/" fails.
5931 - Fix configure.in to not produce broken configure files with
5932 more recent versions of autoconf. Thanks to Clint for his auto*
5934 - Fix security bug on NetBSD that could allow someone to force
5935 uninitialized RAM to be sent to a server's DNS resolver. This
5936 only affects NetBSD and other platforms that do not bounds-check
5938 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
5939 methods: these are known to be buggy.
5940 - If we're a directory mirror and we ask for "all" network status
5941 documents, we would discard status documents from authorities
5945 Changes in version 0.1.1.23 - 2006-07-30
5947 - Fast Tor servers, especially exit nodes, were triggering asserts
5948 due to a bug in handling the list of pending DNS resolves. Some
5949 bugs still remain here; we're hunting them.
5950 - Entry guards could crash clients by sending unexpected input.
5951 - More fixes on reachability testing: if you find yourself reachable,
5952 then don't ever make any client requests (so you stop predicting
5953 circuits), then hup or have your clock jump, then later your IP
5954 changes, you won't think circuits are working, so you won't try to
5955 test reachability, so you won't publish.
5958 - Avoid a crash if the controller does a resetconf firewallports
5959 and then a setconf fascistfirewall=1.
5960 - Avoid an integer underflow when the dir authority decides whether
5961 a router is stable: we might wrongly label it stable, and compute
5962 a slightly wrong median stability, when a descriptor is published
5964 - Fix a place where we might trigger an assert if we can't build our
5965 own server descriptor yet.
5968 Changes in version 0.1.1.22 - 2006-07-05
5970 - Fix a big bug that was causing servers to not find themselves
5971 reachable if they changed IP addresses. Since only 0.1.1.22+
5972 servers can do reachability testing correctly, now we automatically
5973 make sure to test via one of these.
5974 - Fix to allow clients and mirrors to learn directory info from
5975 descriptor downloads that get cut off partway through.
5976 - Directory authorities had a bug in deciding if a newly published
5977 descriptor was novel enough to make everybody want a copy -- a few
5978 servers seem to be publishing new descriptors many times a minute.
5980 - Fix a rare bug that was causing some servers to complain about
5981 "closing wedged cpuworkers" and skip some circuit create requests.
5982 - Make the Exit flag in directory status documents actually work.
5985 Changes in version 0.1.1.21 - 2006-06-10
5986 o Crash and assert fixes from 0.1.1.20:
5987 - Fix a rare crash on Tor servers that have enabled hibernation.
5988 - Fix a seg fault on startup for Tor networks that use only one
5989 directory authority.
5990 - Fix an assert from a race condition that occurs on Tor servers
5991 while exiting, where various threads are trying to log that they're
5992 exiting, and delete the logs, at the same time.
5993 - Make our unit tests pass again on certain obscure platforms.
5996 - Add support for building SUSE RPM packages.
5997 - Speed up initial bootstrapping for clients: if we are making our
5998 first ever connection to any entry guard, then don't mark it down
6000 - When only one Tor server in the network is labelled as a guard,
6001 and we've already picked him, we would cycle endlessly picking him
6002 again, being unhappy about it, etc. Now we specifically exclude
6003 current guards when picking a new guard.
6004 - Servers send create cells more reliably after the TLS connection
6005 is established: we were sometimes forgetting to send half of them
6006 when we had more than one pending.
6007 - If we get a create cell that asks us to extend somewhere, but the
6008 Tor server there doesn't match the expected digest, we now send
6009 a destroy cell back, rather than silently doing nothing.
6010 - Make options->RedirectExit work again.
6011 - Make cookie authentication for the controller work again.
6012 - Stop being picky about unusual characters in the arguments to
6013 mapaddress. It's none of our business.
6014 - Add a new config option "TestVia" that lets you specify preferred
6015 middle hops to use for test circuits. Perhaps this will let me
6016 debug the reachability problems better.
6018 o Log / documentation fixes:
6019 - If we're a server and some peer has a broken TLS certificate, don't
6020 log about it unless ProtocolWarnings is set, i.e., we want to hear
6021 about protocol violations by others.
6022 - Fix spelling of VirtualAddrNetwork in man page.
6023 - Add a better explanation at the top of the autogenerated torrc file
6024 about what happened to our old torrc.
6027 Changes in version 0.1.1.20 - 2006-05-23
6028 o Crash and assert fixes from 0.1.0.17:
6029 - Fix assert bug in close_logs() on exit: when we close and delete
6030 logs, remove them all from the global "logfiles" list.
6031 - Fix an assert error when we're out of space in the connection_list
6032 and we try to post a hidden service descriptor (reported by Peter
6034 - Fix a rare assert error when we've tried all intro points for
6035 a hidden service and we try fetching the service descriptor again:
6036 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed".
6037 - Setconf SocksListenAddress kills Tor if it fails to bind. Now back
6038 out and refuse the setconf if it would fail.
6039 - If you specify a relative torrc path and you set RunAsDaemon in
6040 your torrc, then it chdir()'s to the new directory. If you then
6041 HUP, it tries to load the new torrc location, fails, and exits.
6042 The fix: no longer allow a relative path to torrc when using -f.
6043 - Check for integer overflows in more places, when adding elements
6044 to smartlists. This could possibly prevent a buffer overflow
6045 on malicious huge inputs.
6047 o Security fixes, major:
6048 - When we're printing strings from the network, don't try to print
6049 non-printable characters. Now we're safer against shell escape
6050 sequence exploits, and also against attacks to fool users into
6051 misreading their logs.
6052 - Implement entry guards: automatically choose a handful of entry
6053 nodes and stick with them for all circuits. Only pick new guards
6054 when the ones you have are unsuitable, and if the old guards
6055 become suitable again, switch back. This will increase security
6056 dramatically against certain end-point attacks. The EntryNodes
6057 config option now provides some hints about which entry guards you
6058 want to use most; and StrictEntryNodes means to only use those.
6059 Fixes CVE-2006-0414.
6060 - Implement exit enclaves: if we know an IP address for the
6061 destination, and there's a running Tor server at that address
6062 which allows exit to the destination, then extend the circuit to
6063 that exit first. This provides end-to-end encryption and end-to-end
6064 authentication. Also, if the user wants a .exit address or enclave,
6065 use 4 hops rather than 3, and cannibalize a general circ for it
6067 - Obey our firewall options more faithfully:
6068 . If we can't get to a dirserver directly, try going via Tor.
6069 . Don't ever try to connect (as a client) to a place our
6070 firewall options forbid.
6071 . If we specify a proxy and also firewall options, obey the
6072 firewall options even when we're using the proxy: some proxies
6073 can only proxy to certain destinations.
6074 - Make clients regenerate their keys when their IP address changes.
6075 - For the OS X package's modified privoxy config file, comment
6076 out the "logfile" line so we don't log everything passed
6078 - Our TLS handshakes were generating a single public/private
6079 keypair for the TLS context, rather than making a new one for
6080 each new connection. Oops. (But we were still rotating them
6081 periodically, so it's not so bad.)
6082 - When we were cannibalizing a circuit with a particular exit
6083 node in mind, we weren't checking to see if that exit node was
6084 already present earlier in the circuit. Now we are.
6085 - Require server descriptors to list IPv4 addresses -- hostnames
6086 are no longer allowed. This also fixes potential vulnerabilities
6087 to servers providing hostnames as their address and then
6088 preferentially resolving them so they can partition users.
6089 - Our logic to decide if the OR we connected to was the right guy
6090 was brittle and maybe open to a mitm for invalid routers.
6092 o Security fixes, minor:
6093 - Adjust tor-spec.txt to parameterize cell and key lengths. Now
6094 Ian Goldberg can prove things about our handshake protocol more
6096 - Make directory authorities generate a separate "guard" flag to
6097 mean "would make a good entry guard". Clients now honor the
6098 is_guard flag rather than looking at is_fast or is_stable.
6099 - Try to list MyFamily elements by key, not by nickname, and warn
6100 if we've not heard of a server.
6101 - Start using RAND_bytes rather than RAND_pseudo_bytes from
6102 OpenSSL. Also, reseed our entropy every hour, not just at
6103 startup. And add entropy in 512-bit chunks, not 160-bit chunks.
6104 - Refuse server descriptors where the fingerprint line doesn't match
6105 the included identity key. Tor doesn't care, but other apps (and
6106 humans) might actually be trusting the fingerprint line.
6107 - We used to kill the circuit when we receive a relay command we
6108 don't recognize. Now we just drop that cell.
6109 - Fix a bug found by Lasse Overlier: when we were making internal
6110 circuits (intended to be cannibalized later for rendezvous and
6111 introduction circuits), we were picking them so that they had
6112 useful exit nodes. There was no need for this, and it actually
6113 aids some statistical attacks.
6114 - Start treating internal circuits and exit circuits separately.
6115 It's important to keep them separate because internal circuits
6116 have their last hops picked like middle hops, rather than like
6117 exit hops. So exiting on them will break the user's expectations.
6118 - Fix a possible way to DoS dirservers.
6119 - When the client asked for a rendezvous port that the hidden
6120 service didn't want to provide, we were sending an IP address
6121 back along with the end cell. Fortunately, it was zero. But stop
6124 o Packaging improvements:
6125 - Implement --with-libevent-dir option to ./configure. Improve
6126 search techniques to find libevent, and use those for openssl too.
6127 - Fix a couple of bugs in OpenSSL detection. Deal better when
6128 there are multiple SSLs installed with different versions.
6129 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
6130 - On non-gcc compilers (e.g. Solaris's cc), use "-g -O" instead of
6132 - Make unit tests (and other invocations that aren't the real Tor)
6133 run without launching listeners, creating subdirectories, and so on.
6134 - The OS X installer was adding a symlink for tor_resolve but
6135 the binary was called tor-resolve (reported by Thomas Hardly).
6136 - Now we can target arch and OS in rpm builds (contributed by
6137 Phobos). Also make the resulting dist-rpm filename match the
6139 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
6140 if you log to syslog and want something other than LOG_DAEMON.
6141 - Fix the torify (tsocks) config file to not use Tor for localhost
6143 - Start shipping socks-extensions.txt, tor-doc-unix.html,
6144 tor-doc-server.html, and stylesheet.css in the tarball.
6145 - Stop shipping tor-doc.html, INSTALL, and README in the tarball.
6146 They are useless now.
6147 - Add Peter Palfrader's contributed check-tor script. It lets you
6148 easily check whether a given server (referenced by nickname)
6149 is reachable by you.
6150 - Add BSD-style contributed startup script "rc.subr" from Peter
6153 o Directory improvements -- new directory protocol:
6154 - See tor/doc/dir-spec.txt for all the juicy details. Key points:
6155 - Authorities and caches publish individual descriptors (by
6156 digest, by fingerprint, by "all", and by "tell me yours").
6157 - Clients don't download or use the old directory anymore. Now they
6158 download network-statuses from the directory authorities, and
6159 fetch individual server descriptors as needed from mirrors.
6160 - Clients don't download descriptors of non-running servers.
6161 - Download descriptors by digest, not by fingerprint. Caches try to
6162 download all listed digests from authorities; clients try to
6163 download "best" digests from caches. This avoids partitioning
6164 and isolating attacks better.
6165 - Only upload a new server descriptor when options change, 18
6166 hours have passed, uptime is reset, or bandwidth changes a lot.
6167 - Directory authorities silently throw away new descriptors that
6168 haven't changed much if the timestamps are similar. We do this to
6169 tolerate older Tor servers that upload a new descriptor every 15
6170 minutes. (It seemed like a good idea at the time.)
6171 - Clients choose directory servers from the network status lists,
6172 not from their internal list of router descriptors. Now they can
6173 go to caches directly rather than needing to go to authorities
6174 to bootstrap the first set of descriptors.
6175 - When picking a random directory, prefer non-authorities if any
6177 - Add a new flag to network-status indicating whether the server
6178 can answer v2 directory requests too.
6179 - Directory mirrors now cache up to 16 unrecognized network-status
6180 docs, so new directory authorities will be cached too.
6181 - Stop parsing, storing, or using running-routers output (but
6182 mirrors still cache and serve it).
6183 - Clients consider a threshold of "versioning" directory authorities
6184 before deciding whether to warn the user that he's obsolete.
6185 - Authorities publish separate sorted lists of recommended versions
6186 for clients and for servers.
6187 - Change DirServers config line to note which dirs are v1 authorities.
6188 - Put nicknames on the DirServer line, so we can refer to them
6189 without requiring all our users to memorize their IP addresses.
6190 - Remove option when getting directory cache to see whether they
6191 support running-routers; they all do now. Replace it with one
6192 to see whether caches support v2 stuff.
6193 - Stop listing down or invalid nodes in the v1 directory. This
6194 reduces its bulk by about 1/3, and reduces load on mirrors.
6195 - Mirrors no longer cache the v1 directory as often.
6196 - If we as a directory mirror don't know of any v1 directory
6197 authorities, then don't try to cache any v1 directories.
6199 o Other directory improvements:
6200 - Add lefkada.eecs.harvard.edu and tor.dizum.com as fourth and
6201 fifth authoritative directory servers.
6202 - Directory authorities no longer require an open connection from
6203 a server to consider him "reachable". We need this change because
6204 when we add new directory authorities, old servers won't know not
6206 - Dir authorities now do their own external reachability testing
6207 of each server, and only list as running the ones they found to
6208 be reachable. We also send back warnings to the server's logs if
6209 it uploads a descriptor that we already believe is unreachable.
6210 - Spread the directory authorities' reachability testing over the
6211 entire testing interval, so we don't try to do 500 TLS's at once
6213 - Make the "stable" router flag in network-status be the median of
6214 the uptimes of running valid servers, and make clients pay
6215 attention to the network-status flags. Thus the cutoff adapts
6216 to the stability of the network as a whole, making IRC, IM, etc
6217 connections more reliable.
6218 - Make the v2 dir's "Fast" flag based on relative capacity, just
6219 like "Stable" is based on median uptime. Name everything in the
6220 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
6221 - Retry directory requests if we fail to get an answer we like
6222 from a given dirserver (we were retrying before, but only if
6223 we fail to connect).
6224 - Return a robots.txt on our dirport to discourage google indexing.
6226 o Controller protocol improvements:
6227 - Revised controller protocol (version 1) that uses ascii rather
6228 than binary: tor/doc/control-spec.txt. Add supporting libraries
6229 in python and java and c# so you can use the controller from your
6230 applications without caring how our protocol works.
6231 - Allow the DEBUG controller event to work again. Mark certain log
6232 entries as "don't tell this to controllers", so we avoid cycles.
6233 - New controller function "getinfo accounting", to ask how
6234 many bytes we've used in this time period.
6235 - Add a "resetconf" command so you can set config options like
6236 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
6237 a config option in the torrc with no value, then it clears it
6238 entirely (rather than setting it to its default).
6239 - Add a "getinfo config-file" to tell us where torrc is. Also
6240 expose guard nodes, config options/names.
6241 - Add a "quit" command (when when using the controller manually).
6242 - Add a new signal "newnym" to "change pseudonyms" -- that is, to
6243 stop using any currently-dirty circuits for new streams, so we
6244 don't link new actions to old actions. This also occurs on HUP
6246 - If we would close a stream early (e.g. it asks for a .exit that
6247 we know would refuse it) but the LeaveStreamsUnattached config
6248 option is set by the controller, then don't close it.
6249 - Add a new controller event type "authdir_newdescs" that allows
6250 controllers to get all server descriptors that were uploaded to
6251 a router in its role as directory authority.
6252 - New controller option "getinfo desc/all-recent" to fetch the
6253 latest server descriptor for every router that Tor knows about.
6254 - Fix the controller's "attachstream 0" command to treat conn like
6255 it just connected, doing address remapping, handling .exit and
6256 .onion idioms, and so on. Now we're more uniform in making sure
6257 that the controller hears about new and closing connections.
6258 - Permit transitioning from ORPort==0 to ORPort!=0, and back, from
6259 the controller. Also, rotate dns and cpu workers if the controller
6260 changes options that will affect them; and initialize the dns
6261 worker cache tree whether or not we start out as a server.
6262 - Add a new circuit purpose 'controller' to let the controller ask
6263 for a circuit that Tor won't try to use. Extend the "extendcircuit"
6264 controller command to let you specify the purpose if you're starting
6265 a new circuit. Add a new "setcircuitpurpose" controller command to
6266 let you change a circuit's purpose after it's been created.
6267 - Let the controller ask for "getinfo dir/server/foo" so it can ask
6268 directly rather than connecting to the dir port. "getinfo
6269 dir/status/foo" also works, but currently only if your DirPort
6271 - Let the controller tell us about certain router descriptors
6272 that it doesn't want Tor to use in circuits. Implement
6273 "setrouterpurpose" and modify "+postdescriptor" to do this.
6274 - If the controller's *setconf commands fail, collect an error
6275 message in a string and hand it back to the controller -- don't
6276 just tell them to go read their logs.
6278 o Scalability, resource management, and performance:
6279 - Fix a major load balance bug: we were round-robin reading in 16 KB
6280 chunks, and servers with bandwidthrate of 20 KB, while downloading
6281 a 600 KB directory, would starve their other connections. Now we
6282 try to be a bit more fair.
6283 - Be more conservative about whether to advertise our DirPort.
6284 The main change is to not advertise if we're running at capacity
6285 and either a) we could hibernate ever or b) our capacity is low
6286 and we're using a default DirPort.
6287 - We weren't cannibalizing circuits correctly for
6288 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
6289 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
6290 build those from scratch. This should make hidden services faster.
6291 - Predict required circuits better, with an eye toward making hidden
6292 services faster on the service end.
6293 - Compress exit policies even more: look for duplicate lines and
6295 - Generate 18.0.0.0/8 address policy format in descs when we can;
6296 warn when the mask is not reducible to a bit-prefix.
6297 - There used to be two ways to specify your listening ports in a
6298 server descriptor: on the "router" line and with a separate "ports"
6299 line. Remove support for the "ports" line.
6300 - Reduce memory requirements in our structs by changing the order
6301 of fields. Replace balanced trees with hash tables. Inline
6302 bottleneck smartlist functions. Add a "Map from digest to void*"
6303 abstraction so we can do less hex encoding/decoding, and use it
6304 in router_get_by_digest(). Many other CPU and memory improvements.
6305 - Allow tor_gzip_uncompress to extract as much as possible from
6306 truncated compressed data. Try to extract as many
6307 descriptors as possible from truncated http responses (when
6308 purpose is DIR_PURPOSE_FETCH_ROUTERDESC).
6309 - Make circ->onionskin a pointer, not a static array. moria2 was using
6310 125000 circuit_t's after it had been up for a few weeks, which
6311 translates to 20+ megs of wasted space.
6312 - The private half of our EDH handshake keys are now chosen out
6313 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
6314 - Stop doing the complex voodoo overkill checking for insecure
6315 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
6316 - Do round-robin writes for TLS of at most 16 kB per write. This
6317 might be more fair on loaded Tor servers.
6318 - Do not use unaligned memory access on alpha, mips, or mipsel.
6319 It *works*, but is very slow, so we treat them as if it doesn't.
6321 o Other bugfixes and improvements:
6322 - Start storing useful information to $DATADIR/state, so we can
6323 remember things across invocations of Tor. Retain unrecognized
6324 lines so we can be forward-compatible, and write a TorVersion line
6325 so we can be backward-compatible.
6326 - If ORPort is set, Address is not explicitly set, and our hostname
6327 resolves to a private IP address, try to use an interface address
6328 if it has a public address. Now Windows machines that think of
6329 themselves as localhost can guess their address.
6330 - Regenerate our local descriptor if it's dirty and we try to use
6331 it locally (e.g. if it changes during reachability detection).
6332 This was causing some Tor servers to keep publishing the same
6333 initial descriptor forever.
6334 - Tor servers with dynamic IP addresses were needing to wait 18
6335 hours before they could start doing reachability testing using
6336 the new IP address and ports. This is because they were using
6337 the internal descriptor to learn what to test, yet they were only
6338 rebuilding the descriptor once they decided they were reachable.
6339 - It turns out we couldn't bootstrap a network since we added
6340 reachability detection in 0.1.0.1-rc. Good thing the Tor network
6341 has never gone down. Add an AssumeReachable config option to let
6342 servers and authorities bootstrap. When we're trying to build a
6343 high-uptime or high-bandwidth circuit but there aren't enough
6344 suitable servers, try being less picky rather than simply failing.
6345 - Newly bootstrapped Tor networks couldn't establish hidden service
6346 circuits until they had nodes with high uptime. Be more tolerant.
6347 - Really busy servers were keeping enough circuits open on stable
6348 connections that they were wrapping around the circuit_id
6349 space. (It's only two bytes.) This exposed a bug where we would
6350 feel free to reuse a circuit_id even if it still exists but has
6351 been marked for close. Try to fix this bug. Some bug remains.
6352 - When we fail to bind or listen on an incoming or outgoing
6353 socket, we now close it before refusing, rather than just
6354 leaking it. (Thanks to Peter Palfrader for finding.)
6355 - Fix a file descriptor leak in start_daemon().
6356 - On Windows, you can't always reopen a port right after you've
6357 closed it. So change retry_listeners() to only close and re-open
6358 ports that have changed.
6359 - Workaround a problem with some http proxies that refuse GET
6360 requests that specify "Content-Length: 0". Reported by Adrian.
6361 - Recover better from TCP connections to Tor servers that are
6362 broken but don't tell you (it happens!); and rotate TLS
6363 connections once a week.
6364 - Fix a scary-looking but apparently harmless bug where circuits
6365 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
6366 servers, and never switch to state CIRCUIT_STATE_OPEN.
6367 - Check for even more Windows version flags when writing the platform
6368 string in server descriptors, and note any we don't recognize.
6369 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
6370 get a better idea of why their circuits failed. Not used yet.
6371 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
6372 We don't use them yet, but maybe one day our DNS resolver will be
6373 able to discover them.
6374 - Let people type "tor --install" as well as "tor -install" when they
6375 want to make it an NT service.
6376 - Looks like we were never delivering deflated (i.e. compressed)
6377 running-routers lists, even when asked. Oops.
6378 - We were leaking some memory every time the client changed IPs.
6379 - Clean up more of the OpenSSL memory when exiting, so we can detect
6380 memory leaks better.
6381 - Never call free() on tor_malloc()d memory. This will help us
6382 use dmalloc to detect memory leaks.
6383 - Some Tor servers process billions of cells per day. These
6384 statistics are now uint64_t's.
6385 - Check [X-]Forwarded-For headers in HTTP requests when generating
6386 log messages. This lets people run dirservers (and caches) behind
6387 Apache but still know which IP addresses are causing warnings.
6388 - Fix minor integer overflow in calculating when we expect to use up
6389 our bandwidth allocation before hibernating.
6390 - Lower the minimum required number of file descriptors to 1000,
6391 so we can have some overhead for Valgrind on Linux, where the
6392 default ulimit -n is 1024.
6393 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
6394 and its existence is confusing some users.
6396 o Config option fixes:
6397 - Add a new config option ExitPolicyRejectPrivate which defaults
6398 to on. Now all exit policies will begin with rejecting private
6399 addresses, unless the server operator explicitly turns it off.
6400 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB.
6401 - Add new ReachableORAddresses and ReachableDirAddresses options
6402 that understand address policies. FascistFirewall is now a synonym
6403 for "ReachableORAddresses *:443", "ReachableDirAddresses *:80".
6404 - Start calling it FooListenAddress rather than FooBindAddress,
6405 since few of our users know what it means to bind an address
6407 - If the user gave Tor an odd number of command-line arguments,
6408 we were silently ignoring the last one. Now we complain and fail.
6409 This wins the oldest-bug prize -- this bug has been present since
6410 November 2002, as released in Tor 0.0.0.
6411 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
6412 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
6413 it would silently ignore the 6668.
6414 - If we get a linelist or linelist_s config option from the torrc,
6415 e.g. ExitPolicy, and it has no value, warn and skip rather than
6416 silently resetting it to its default.
6417 - Setconf was appending items to linelists, not clearing them.
6418 - Add MyFamily to torrc.sample in the server section, so operators
6419 will be more likely to learn that it exists.
6420 - Make ContactInfo mandatory for authoritative directory servers.
6421 - MaxConn has been obsolete for a while now. Document the ConnLimit
6422 config option, which is a *minimum* number of file descriptors
6423 that must be available else Tor refuses to start.
6424 - Get rid of IgnoreVersion undocumented config option, and make us
6425 only warn, never exit, when we're running an obsolete version.
6426 - Make MonthlyAccountingStart config option truly obsolete now.
6427 - Correct the man page entry on TrackHostExitsExpire.
6428 - Let directory authorities start even if they don't specify an
6429 Address config option.
6430 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
6431 reflect the updated flags in our v2 dir protocol.
6433 o Config option features:
6434 - Add a new config option FastFirstHopPK (on by default) so clients
6435 do a trivial crypto handshake for their first hop, since TLS has
6436 already taken care of confidentiality and authentication.
6437 - Let the user set ControlListenAddress in the torrc. This can be
6438 dangerous, but there are some cases (like a secured LAN) where it
6440 - New config options to help controllers: FetchServerDescriptors
6441 and FetchHidServDescriptors for whether to fetch server
6442 info and hidserv info or let the controller do it, and
6443 PublishServerDescriptor and PublishHidServDescriptors.
6444 - Also let the controller set the __AllDirActionsPrivate config
6445 option if you want all directory fetches/publishes to happen via
6446 Tor (it assumes your controller bootstraps your circuits).
6447 - Add "HardwareAccel" config option: support for crypto hardware
6448 accelerators via OpenSSL. Off by default, until we find somebody
6449 smart who can test it for us. (It appears to produce seg faults
6450 in at least some cases.)
6451 - New config option "AuthDirRejectUnlisted" for directory authorities
6452 as a panic button: if we get flooded with unusable servers we can
6453 revert to only listing servers in the approved-routers file.
6454 - Directory authorities can now reject/invalidate by key and IP,
6455 with the config options "AuthDirInvalid" and "AuthDirReject", or
6456 by marking a fingerprint as "!reject" or "!invalid" (as its
6457 nickname) in the approved-routers file. This is useful since
6458 currently we automatically list servers as running and usable
6459 even if we know they're jerks.
6460 - Add a new config option TestSocks so people can see whether their
6461 applications are using socks4, socks4a, socks5-with-ip, or
6462 socks5-with-fqdn. This way they don't have to keep mucking
6463 with tcpdump and wondering if something got cached somewhere.
6464 - Add "private:*" as an alias in configuration for policies. Now
6465 you can simplify your exit policy rather than needing to list
6466 every single internal or nonroutable network space.
6467 - Accept "private:*" in routerdesc exit policies; not generated yet
6468 because older Tors do not understand it.
6469 - Add configuration option "V1AuthoritativeDirectory 1" which
6470 moria1, moria2, and tor26 have set.
6471 - Implement an option, VirtualAddrMask, to set which addresses
6472 get handed out in response to mapaddress requests. This works
6473 around a bug in tsocks where 127.0.0.0/8 is never socksified.
6474 - Add a new config option FetchUselessDescriptors, off by default,
6475 for when you plan to run "exitlist" on your client and you want
6476 to know about even the non-running descriptors.
6477 - SocksTimeout: How long do we let a socks connection wait
6478 unattached before we fail it?
6479 - CircuitBuildTimeout: Cull non-open circuits that were born
6480 at least this many seconds ago.
6481 - CircuitIdleTimeout: Cull open clean circuits that were born
6482 at least this many seconds ago.
6483 - New config option SafeSocks to reject all application connections
6484 using unsafe socks protocols. Defaults to off.
6486 o Improved and clearer log messages:
6487 - Reduce clutter in server logs. We're going to try to make
6488 them actually usable now. New config option ProtocolWarnings that
6489 lets you hear about how _other Tors_ are breaking the protocol. Off
6491 - Divide log messages into logging domains. Once we put some sort
6492 of interface on this, it will let people looking at more verbose
6493 log levels specify the topics they want to hear more about.
6494 - Log server fingerprint on startup, so new server operators don't
6495 have to go hunting around their filesystem for it.
6496 - Provide dire warnings to any users who set DirServer manually;
6497 move it out of torrc.sample and into torrc.complete.
6498 - Make the log message less scary when all the dirservers are
6499 temporarily unreachable.
6500 - When tor_socketpair() fails in Windows, give a reasonable
6501 Windows-style errno back.
6502 - Improve tor_gettimeofday() granularity on windows.
6503 - We were printing the number of idle dns workers incorrectly when
6505 - Handle duplicate lines in approved-routers files without warning.
6506 - We were whining about using socks4 or socks5-with-local-lookup
6507 even when it's an IP address in the "virtual" range we designed
6508 exactly for this case.
6509 - Check for named servers when looking them up by nickname;
6510 warn when we're calling a non-named server by its nickname;
6511 don't warn twice about the same name.
6512 - Downgrade the dirserver log messages when whining about
6514 - Correct "your server is reachable" log entries to indicate that
6515 it was self-testing that told us so.
6516 - If we're trying to be a Tor server and running Windows 95/98/ME
6517 as a server, explain that we'll likely crash.
6518 - Provide a more useful warn message when our onion queue gets full:
6519 the CPU is too slow or the exit policy is too liberal.
6520 - Don't warn when we receive a 503 from a dirserver/cache -- this
6521 will pave the way for them being able to refuse if they're busy.
6522 - When we fail to bind a listener, try to provide a more useful
6523 log message: e.g., "Is Tor already running?"
6524 - Only start testing reachability once we've established a
6525 circuit. This will make startup on dir authorities less noisy.
6526 - Don't try to upload hidden service descriptors until we have
6527 established a circuit.
6528 - Tor didn't warn when it failed to open a log file.
6529 - Warn when listening on a public address for socks. We suspect a
6530 lot of people are setting themselves up as open socks proxies,
6531 and they have no idea that jerks on the Internet are using them,
6532 since they simply proxy the traffic into the Tor network.
6533 - Give a useful message when people run Tor as the wrong user,
6534 rather than telling them to start chowning random directories.
6535 - Fix a harmless bug that was causing Tor servers to log
6536 "Got an end because of misc error, but we're not an AP. Closing."
6537 - Fix wrong log message when you add a "HiddenServiceNodes" config
6538 line without any HiddenServiceDir line (reported by Chris Thomas).
6539 - Directory authorities now stop whining so loudly about bad
6540 descriptors that they fetch from other dirservers. So when there's
6541 a log complaint, it's for sure from a freshly uploaded descriptor.
6542 - When logging via syslog, include the pid whenever we provide
6543 a log entry. Suggested by Todd Fries.
6544 - When we're shutting down and we do something like try to post a
6545 server descriptor or rendezvous descriptor, don't complain that
6546 we seem to be unreachable. Of course we are, we're shutting down.
6547 - Change log line for unreachability to explicitly suggest /etc/hosts
6548 as the culprit. Also make it clearer what IP address and ports we're
6549 testing for reachability.
6550 - Put quotes around user-supplied strings when logging so users are
6551 more likely to realize if they add bad characters (like quotes)
6553 - NT service patch from Matt Edman to improve error messages on Win32.
6556 Changes in version 0.1.0.17 - 2006-02-17
6557 o Crash bugfixes on 0.1.0.x:
6558 - When servers with a non-zero DirPort came out of hibernation,
6559 sometimes they would trigger an assert.
6561 o Other important bugfixes:
6562 - On platforms that don't have getrlimit (like Windows), we were
6563 artificially constraining ourselves to a max of 1024
6564 connections. Now just assume that we can handle as many as 15000
6565 connections. Hopefully this won't cause other problems.
6567 o Backported features:
6568 - When we're a server, a client asks for an old-style directory,
6569 and our write bucket is empty, don't give it to him. This way
6570 small servers can continue to serve the directory *sometimes*,
6571 without getting overloaded.
6572 - Whenever you get a 503 in response to a directory fetch, try
6573 once more. This will become important once servers start sending
6574 503's whenever they feel busy.
6575 - Fetch a new directory every 120 minutes, not every 40 minutes.
6576 Now that we have hundreds of thousands of users running the old
6577 directory algorithm, it's starting to hurt a lot.
6578 - Bump up the period for forcing a hidden service descriptor upload
6579 from 20 minutes to 1 hour.
6582 Changes in version 0.1.0.16 - 2006-01-02
6583 o Crash bugfixes on 0.1.0.x:
6584 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
6585 corrupting the heap, losing FDs, or crashing when we need to resize
6586 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
6587 - It turns out sparc64 platforms crash on unaligned memory access
6588 too -- so detect and avoid this.
6589 - Handle truncated compressed data correctly (by detecting it and
6591 - Fix possible-but-unlikely free(NULL) in control.c.
6592 - When we were closing connections, there was a rare case that
6593 stomped on memory, triggering seg faults and asserts.
6594 - Avoid potential infinite recursion when building a descriptor. (We
6595 don't know that it ever happened, but better to fix it anyway.)
6596 - We were neglecting to unlink marked circuits from soon-to-close OR
6597 connections, which caused some rare scribbling on freed memory.
6598 - Fix a memory stomping race bug when closing the joining point of two
6599 rendezvous circuits.
6600 - Fix an assert in time parsing found by Steven Murdoch.
6602 o Other bugfixes on 0.1.0.x:
6603 - When we're doing reachability testing, provide more useful log
6604 messages so the operator knows what to expect.
6605 - Do not check whether DirPort is reachable when we are suppressing
6606 advertising it because of hibernation.
6607 - When building with -static or on Solaris, we sometimes needed -ldl.
6608 - One of the dirservers (tor26) changed its IP address.
6609 - When we're deciding whether a stream has enough circuits around
6610 that can handle it, count the freshly dirty ones and not the ones
6611 that are so dirty they won't be able to handle it.
6612 - When we're expiring old circuits, we had a logic error that caused
6613 us to close new rendezvous circuits rather than old ones.
6614 - Give a more helpful log message when you try to change ORPort via
6615 the controller: you should upgrade Tor if you want that to work.
6616 - We were failing to parse Tor versions that start with "Tor ".
6617 - Tolerate faulty streams better: when a stream fails for reason
6618 exitpolicy, stop assuming that the router is lying about his exit
6619 policy. When a stream fails for reason misc, allow it to retry just
6620 as if it was resolvefailed. When a stream has failed three times,
6621 reset its failure count so we can try again and get all three tries.
6624 Changes in version 0.1.0.15 - 2005-09-23
6625 o Bugfixes on 0.1.0.x:
6626 - Reject ports 465 and 587 (spam targets) in default exit policy.
6627 - Don't crash when we don't have any spare file descriptors and we
6628 try to spawn a dns or cpu worker.
6629 - Get rid of IgnoreVersion undocumented config option, and make us
6630 only warn, never exit, when we're running an obsolete version.
6631 - Don't try to print a null string when your server finds itself to
6632 be unreachable and the Address config option is empty.
6633 - Make the numbers in read-history and write-history into uint64s,
6634 so they don't overflow and publish negatives in the descriptor.
6635 - Fix a minor memory leak in smartlist_string_remove().
6636 - We were only allowing ourselves to upload a server descriptor at
6637 most every 20 minutes, even if it changed earlier than that.
6638 - Clean up log entries that pointed to old URLs.
6641 Changes in version 0.1.0.14 - 2005-08-08
6642 o Bugfixes on 0.1.0.x:
6643 - Fix the other half of the bug with crypto handshakes
6645 - Fix an assert trigger if you send a 'signal term' via the
6646 controller when it's listening for 'event info' messages.
6649 Changes in version 0.1.0.13 - 2005-08-04
6650 o Bugfixes on 0.1.0.x:
6651 - Fix a critical bug in the security of our crypto handshakes.
6652 - Fix a size_t underflow in smartlist_join_strings2() that made
6653 it do bad things when you hand it an empty smartlist.
6654 - Fix Windows installer to ship Tor license (thanks to Aphex for
6655 pointing out this oversight) and put a link to the doc directory
6657 - Explicitly set no-unaligned-access for sparc: it turns out the
6658 new gcc's let you compile broken code, but that doesn't make it
6662 Changes in version 0.1.0.12 - 2005-07-18
6663 o New directory servers:
6664 - tor26 has changed IP address.
6666 o Bugfixes on 0.1.0.x:
6667 - Fix a possible double-free in tor_gzip_uncompress().
6668 - When --disable-threads is set, do not search for or link against
6670 - Don't trigger an assert if an authoritative directory server
6671 claims its dirport is 0.
6672 - Fix bug with removing Tor as an NT service: some people were
6673 getting "The service did not return an error." Thanks to Matt
6677 Changes in version 0.1.0.11 - 2005-06-30
6678 o Bugfixes on 0.1.0.x:
6679 - Fix major security bug: servers were disregarding their
6680 exit policies if clients behaved unexpectedly.
6681 - Make OS X init script check for missing argument, so we don't
6682 confuse users who invoke it incorrectly.
6683 - Fix a seg fault in "tor --hash-password foo".
6684 - The MAPADDRESS control command was broken.
6687 Changes in version 0.1.0.10 - 2005-06-14
6689 - Make NT services work and start on startup on Win32 (based on
6690 patch by Matt Edman). See the FAQ entry for details.
6691 - Make 'platform' string in descriptor more accurate for Win32
6692 servers, so it's not just "unknown platform".
6693 - REUSEADDR on normal platforms means you can rebind to the port
6694 right after somebody else has let it go. But REUSEADDR on Win32
6695 means you can bind to the port _even when somebody else already
6696 has it bound_! So, don't do that on Win32.
6697 - Clean up the log messages when starting on Win32 with no config
6699 - Allow seeding the RNG on Win32 even when you're not running as
6700 Administrator. If seeding the RNG on Win32 fails, quit.
6702 o Assert / crash bugs:
6703 - Refuse relay cells that claim to have a length larger than the
6704 maximum allowed. This prevents a potential attack that could read
6705 arbitrary memory (e.g. keys) from an exit server's process
6707 - If unofficial Tor clients connect and send weird TLS certs, our
6708 Tor server triggers an assert. Stop asserting, and start handling
6709 TLS errors better in other situations too.
6710 - Fix a race condition that can trigger an assert when we have a
6711 pending create cell and an OR connection attempt fails.
6714 - Use pthreads for worker processes rather than forking. This was
6715 forced because when we forked, we ended up wasting a lot of
6716 duplicate ram over time.
6717 - Also switch to foo_r versions of some library calls to allow
6718 reentry and threadsafeness.
6719 - Implement --disable-threads configure option. Disable threads on
6720 netbsd and openbsd by default, because they have no reentrant
6721 resolver functions (!), and on solaris since it has other
6723 - Fix possible bug on threading platforms (e.g. win32) which was
6724 leaking a file descriptor whenever a cpuworker or dnsworker died.
6725 - Fix a minor memory leak when somebody establishes an introduction
6726 point at your Tor server.
6727 - Fix possible memory leak in tor_lookup_hostname(). (Thanks to
6729 - Add ./configure --with-dmalloc option, to track memory leaks.
6730 - And try to free all memory on closing, so we can detect what
6733 o Protocol correctness:
6734 - When we've connected to an OR and handshaked but didn't like
6735 the result, we were closing the conn without sending destroy
6736 cells back for pending circuits. Now send those destroys.
6737 - Start sending 'truncated' cells back rather than destroy cells
6738 if the circuit closes in front of you. This means we won't have
6739 to abandon partially built circuits.
6740 - Handle changed router status correctly when dirserver reloads
6741 fingerprint file. We used to be dropping all unverified descriptors
6742 right then. The bug was hidden because we would immediately
6743 fetch a directory from another dirserver, which would include the
6744 descriptors we just dropped.
6745 - Revise tor-spec to add more/better stream end reasons.
6746 - Revise all calls to connection_edge_end to avoid sending 'misc',
6747 and to take errno into account where possible.
6748 - Client now retries when streams end early for 'hibernating' or
6749 'resource limit' reasons, rather than failing them.
6750 - Try to be more zealous about calling connection_edge_end when
6751 things go bad with edge conns in connection.c.
6753 o Robustness improvements:
6754 - Better handling for heterogeneous / unreliable nodes:
6755 - Annotate circuits with whether they aim to contain high uptime
6756 nodes and/or high capacity nodes. When building circuits, choose
6758 - This means that every single node in an intro rend circuit,
6759 not just the last one, will have a minimum uptime.
6760 - New config option LongLivedPorts to indicate application streams
6761 that will want high uptime circuits.
6762 - Servers reset uptime when a dir fetch entirely fails. This
6763 hopefully reflects stability of the server's network connectivity.
6764 - If somebody starts his tor server in Jan 2004 and then fixes his
6765 clock, don't make his published uptime be a year.
6766 - Reset published uptime when we wake up from hibernation.
6767 - Introduce a notion of 'internal' circs, which are chosen without
6768 regard to the exit policy of the last hop. Intro and rendezvous
6769 circs must be internal circs, to avoid leaking information. Resolve
6770 and connect streams can use internal circs if they want.
6771 - New circuit pooling algorithm: keep track of what destination ports
6772 we've used recently (start out assuming we'll want to use 80), and
6773 make sure to have enough circs around to satisfy these ports. Also
6774 make sure to have 2 internal circs around if we've required internal
6775 circs lately (and with high uptime if we've seen that lately too).
6776 - Turn addr_policy_compare from a tristate to a quadstate; this should
6777 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
6778 for google.com" problem.
6779 - When a client asks us for a dir mirror and we don't have one,
6780 launch an attempt to get a fresh one.
6781 - First cut at support for "create-fast" cells. Clients can use
6782 these when extending to their first hop, since the TLS already
6783 provides forward secrecy and authentication. Not enabled on
6786 o Reachability testing.
6787 - Your Tor server will automatically try to see if its ORPort and
6788 DirPort are reachable from the outside, and it won't upload its
6789 descriptor until it decides at least ORPort is reachable (when
6790 DirPort is not yet found reachable, publish it as zero).
6791 - When building testing circs for ORPort testing, use only
6792 high-bandwidth nodes, so fewer circuits fail.
6793 - Notice when our IP changes, and reset stats/uptime/reachability.
6794 - Authdirservers don't do ORPort reachability detection, since
6795 they're in clique mode, so it will be rare to find a server not
6796 already connected to them.
6797 - Authdirservers now automatically approve nodes running 0.1.0.2-rc
6801 - Now we allow two unverified servers with the same nickname
6802 but different keys. But if a nickname is verified, only that
6803 nickname+key are allowed.
6804 - If you're an authdirserver connecting to an address:port,
6805 and it's not the OR you were expecting, forget about that
6806 descriptor. If he *was* the one you were expecting, then forget
6807 about all other descriptors for that address:port.
6808 - Allow servers to publish descriptors from 12 hours in the future.
6809 Corollary: only whine about clock skew from the dirserver if
6810 he's a trusted dirserver (since now even verified servers could
6811 have quite wrong clocks).
6812 - Require servers that use the default dirservers to have public IP
6813 addresses. We have too many servers that are configured with private
6814 IPs and their admins never notice the log entries complaining that
6815 their descriptors are being rejected.
6817 o Efficiency improvements:
6818 - Use libevent. Now we can use faster async cores (like epoll, kpoll,
6819 and /dev/poll), and hopefully work better on Windows too.
6820 - Apple's OS X 10.4.0 ships with a broken kqueue API, and using
6821 kqueue on 10.3.9 causes kernel panics. Don't use kqueue on OS X.
6822 - Find libevent even if it's hiding in /usr/local/ and your
6823 CFLAGS and LDFLAGS don't tell you to look there.
6824 - Be able to link with libevent as a shared library (the default
6825 after 1.0d), even if it's hiding in /usr/local/lib and even
6826 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
6827 assuming you're running gcc. Otherwise fail and give a useful
6829 - Switch to a new buffer management algorithm, which tries to avoid
6830 reallocing and copying quite as much. In first tests it looks like
6831 it uses *more* memory on average, but less cpu.
6832 - Switch our internal buffers implementation to use a ring buffer,
6833 to hopefully improve performance for fast servers a lot.
6834 - Reenable the part of the code that tries to flush as soon as an
6835 OR outbuf has a full TLS record available. Perhaps this will make
6836 OR outbufs not grow as huge except in rare cases, thus saving lots
6837 of CPU time plus memory.
6838 - Improve performance for dirservers: stop re-parsing the whole
6839 directory every time you regenerate it.
6840 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
6841 it much faster to look up a circuit for each relay cell.
6842 - Remove most calls to assert_all_pending_dns_resolves_ok(),
6843 since they're eating our cpu on exit nodes.
6844 - Stop wasting time doing a case insensitive comparison for every
6845 dns name every time we do any lookup. Canonicalize the names to
6846 lowercase when you first see them.
6849 - Handle unavailable hidden services better. Handle slow or busy
6850 hidden services better.
6851 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
6852 circ as necessary, if there are any completed ones lying around
6853 when we try to launch one.
6854 - Make hidden services try to establish a rendezvous for 30 seconds
6855 after fetching the descriptor, rather than for n (where n=3)
6856 attempts to build a circuit.
6857 - Adjust maximum skew and age for rendezvous descriptors: let skew
6858 be 48 hours rather than 90 minutes.
6859 - Reject malformed .onion addresses rather then passing them on as
6860 normal web requests.
6863 - More Tor controller support. See
6864 http://tor.eff.org/doc/control-spec.txt for all the new features,
6865 including signals to emulate unix signals from any platform;
6866 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
6867 closestream; closecircuit; etc.
6868 - Encode hashed controller passwords in hex instead of base64,
6869 to make it easier to write controllers.
6870 - Revise control spec and implementation to allow all log messages to
6871 be sent to controller with their severities intact (suggested by
6872 Matt Edman). Disable debug-level logs while delivering a debug-level
6873 log to the controller, to prevent loop. Update TorControl to handle
6874 new log event types.
6876 o New config options/defaults:
6877 - Begin scrubbing sensitive strings from logs by default. Turn off
6878 the config option SafeLogging if you need to do debugging.
6879 - New exit policy: accept most low-numbered ports, rather than
6880 rejecting most low-numbered ports.
6881 - Put a note in the torrc about abuse potential with the default
6883 - Add support for CONNECTing through https proxies, with "HttpsProxy"
6885 - Add HttpProxyAuthenticator and HttpsProxyAuthenticator support
6886 based on patch from Adam Langley (basic auth only).
6887 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
6888 the fast servers that have been joining lately. (Clients are now
6889 willing to load balance over up to 2 MB of advertised bandwidth
6891 - New config option MaxAdvertisedBandwidth which lets you advertise
6892 a low bandwidthrate (to not attract as many circuits) while still
6893 allowing a higher bandwidthrate in reality.
6894 - Require BandwidthRate to be at least 20kB/s for servers.
6895 - Add a NoPublish config option, so you can be a server (e.g. for
6896 testing running Tor servers in other Tor networks) without
6897 publishing your descriptor to the primary dirservers.
6898 - Add a new AddressMap config directive to rewrite incoming socks
6899 addresses. This lets you, for example, declare an implicit
6900 required exit node for certain sites.
6901 - Add a new TrackHostExits config directive to trigger addressmaps
6902 for certain incoming socks addresses -- for sites that break when
6903 your exit keeps changing (based on patch from Mike Perry).
6904 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
6905 which describes how often we retry making new circuits if current
6906 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
6907 how long we're willing to make use of an already-dirty circuit.
6908 - Change compiled-in SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to
6909 a config option "ShutdownWaitLength" (when using kill -INT on
6911 - Fix an edge case in parsing config options: if they say "--"
6912 on the commandline, it's not a config option (thanks weasel).
6913 - New config option DirAllowPrivateAddresses for authdirservers.
6914 Now by default they refuse router descriptors that have non-IP or
6915 private-IP addresses.
6916 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
6917 smart" default value: low for servers and high for clients.
6918 - Some people were putting "Address " in their torrc, and they had
6919 a buggy resolver that resolved " " to 0.0.0.0. Oops.
6920 - If DataDir is ~/.tor, and that expands to /.tor, then default to
6921 LOCALSTATEDIR/tor instead.
6922 - Implement --verify-config command-line option to check if your torrc
6923 is valid without actually launching Tor.
6925 o Logging improvements:
6926 - When dirservers refuse a server descriptor, we now log its
6927 contactinfo, platform, and the poster's IP address.
6928 - Only warn once per nickname from add_nickname_list_to_smartlist()
6929 per failure, so an entrynode or exitnode choice that's down won't
6931 - When we're connecting to an OR and he's got a different nickname/key
6932 than we were expecting, only complain loudly if we're an OP or a
6933 dirserver. Complaining loudly to the OR admins just confuses them.
6934 - Whine at you if you're a server and you don't set your contactinfo.
6935 - Warn when exit policy implicitly allows local addresses.
6936 - Give a better warning when some other server advertises an
6937 ORPort that is actually an apache running ssl.
6938 - If we get an incredibly skewed timestamp from a dirserver mirror
6939 that isn't a verified OR, don't warn -- it's probably him that's
6941 - When a dirserver causes you to give a warn, mention which dirserver
6943 - Initialize libevent later in the startup process, so the logs are
6944 already established by the time we start logging libevent warns.
6945 - Use correct errno on win32 if libevent fails.
6946 - Check and warn about known-bad/slow libevent versions.
6947 - Stop warning about sigpipes in the logs. We're going to
6948 pretend that getting these occassionally is normal and fine.
6950 o New contrib scripts:
6951 - New experimental script tor/contrib/exitlist: a simple python
6952 script to parse directories and find Tor nodes that exit to listed
6954 - New experimental script tor/contrib/ExerciseServer.py (needs more
6955 work) that uses the controller interface to build circuits and
6956 fetch pages over them. This will help us bootstrap servers that
6957 have lots of capacity but haven't noticed it yet.
6958 - New experimental script tor/contrib/PathDemo.py (needs more work)
6959 that uses the controller interface to let you choose whole paths
6961 "<hostname>.<path,separated by dots>.<length of path>.path"
6962 - New contributed script "privoxy-tor-toggle" to toggle whether
6963 Privoxy uses Tor. Seems to be configured for Debian by default.
6964 - Have torctl.in/tor.sh.in check for location of su binary (needed
6968 - chdir() to your datadirectory at the *end* of the daemonize process,
6969 not the beginning. This was a problem because the first time you
6970 run tor, if your datadir isn't there, and you have runasdaemon set
6971 to 1, it will try to chdir to it before it tries to create it. Oops.
6972 - Fix several double-mark-for-close bugs, e.g. where we were finding
6973 a conn for a cell even if that conn is already marked for close.
6974 - Stop most cases of hanging up on a socks connection without sending
6976 - Fix a bug in the RPM package: set home directory for _tor to
6977 something more reasonable when first installing.
6978 - Stop putting nodename in the Platform string in server descriptors.
6979 It doesn't actually help, and it is confusing/upsetting some people.
6980 - When using preferred entry or exit nodes, ignore whether the
6981 circuit wants uptime or capacity. They asked for the nodes, they
6983 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
6984 artificially capped at 500kB.
6985 - Cache local dns resolves correctly even when they're .exit
6987 - If we're hibernating and we get a SIGINT, exit immediately.
6988 - tor-resolve requests were ignoring .exit if there was a working circuit
6989 they could use instead.
6990 - Pay more attention to the ClientOnly config option.
6991 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in certain
6992 installer screens; and don't put stuff into StartupItems unless
6993 the user asks you to.
6996 - Rewrite address "serifos.exit" to "externalIP.serifos.exit"
6997 rather than just rejecting it.
6998 - If our clock jumps forward by 100 seconds or more, assume something
6999 has gone wrong with our network and abandon all not-yet-used circs.
7000 - When an application is using socks5, give him the whole variety of
7001 potential socks5 responses (connect refused, host unreachable, etc),
7002 rather than just "success" or "failure".
7003 - A more sane version numbering system. See
7004 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
7005 - Change version parsing logic: a version is "obsolete" if it is not
7006 recommended and (1) there is a newer recommended version in the
7007 same series, or (2) there are no recommended versions in the same
7008 series, but there are some recommended versions in a newer series.
7009 A version is "new" if it is newer than any recommended version in
7011 - Report HTTP reasons to client when getting a response from directory
7012 servers -- so you can actually know what went wrong.
7013 - Reject odd-looking addresses at the client (e.g. addresses that
7014 contain a colon), rather than having the server drop them because
7016 - Stop publishing socksport in the directory, since it's not
7017 actually meant to be public. For compatibility, publish a 0 there
7019 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
7020 cookies to disk and doesn't log each web request to disk. (Thanks
7021 to Brett Carrington for pointing this out.)
7022 - Add OSX uninstall instructions. An actual uninstall script will
7024 - Add "opt hibernating 1" to server descriptor to make it clearer
7025 whether the server is hibernating.
7028 Changes in version 0.0.9.10 - 2005-06-16
7029 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
7030 - Refuse relay cells that claim to have a length larger than the
7031 maximum allowed. This prevents a potential attack that could read
7032 arbitrary memory (e.g. keys) from an exit server's process
7036 Changes in version 0.0.9.9 - 2005-04-23
7037 o Bugfixes on 0.0.9.x:
7038 - If unofficial Tor clients connect and send weird TLS certs, our
7039 Tor server triggers an assert. This release contains a minimal
7040 backport from the broader fix that we put into 0.1.0.4-rc.
7043 Changes in version 0.0.9.8 - 2005-04-07
7044 o Bugfixes on 0.0.9.x:
7045 - We have a bug that I haven't found yet. Sometimes, very rarely,
7046 cpuworkers get stuck in the 'busy' state, even though the cpuworker
7047 thinks of itself as idle. This meant that no new circuits ever got
7048 established. Here's a workaround to kill any cpuworker that's been
7049 busy for more than 100 seconds.
7052 Changes in version 0.0.9.7 - 2005-04-01
7053 o Bugfixes on 0.0.9.x:
7054 - Fix another race crash bug (thanks to Glenn Fink for reporting).
7055 - Compare identity to identity, not to nickname, when extending to
7056 a router not already in the directory. This was preventing us from
7057 extending to unknown routers. Oops.
7058 - Make sure to create OS X Tor user in <500 range, so we aren't
7059 creating actual system users.
7060 - Note where connection-that-hasn't-sent-end was marked, and fix
7061 a few really loud instances of this harmless bug (it's fixed more
7065 Changes in version 0.0.9.6 - 2005-03-24
7066 o Bugfixes on 0.0.9.x (crashes and asserts):
7067 - Add new end stream reasons to maintainance branch. Fix bug where
7068 reason (8) could trigger an assert. Prevent bug from recurring.
7069 - Apparently win32 stat wants paths to not end with a slash.
7070 - Fix assert triggers in assert_cpath_layer_ok(), where we were
7071 blowing away the circuit that conn->cpath_layer points to, then
7072 checking to see if the circ is well-formed. Backport check to make
7073 sure we dont use the cpath on a closed connection.
7074 - Prevent circuit_resume_edge_reading_helper() from trying to package
7075 inbufs for marked-for-close streams.
7076 - Don't crash on hup if your options->address has become unresolvable.
7077 - Some systems (like OS X) sometimes accept() a connection and tell
7078 you the remote host is 0.0.0.0:0. If this happens, due to some
7079 other mis-features, we get confused; so refuse the conn for now.
7081 o Bugfixes on 0.0.9.x (other):
7082 - Fix harmless but scary "Unrecognized content encoding" warn message.
7083 - Add new stream error reason: TORPROTOCOL reason means "you are not
7084 speaking a version of Tor I understand; say bye-bye to your stream."
7085 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
7086 into the future, now that we are more tolerant of skew. This
7087 resolves a bug where a Tor server would refuse to cache a directory
7088 because all the directories it gets are too far in the future;
7089 yet the Tor server never logs any complaints about clock skew.
7090 - Mac packaging magic: make man pages useable, and do not overwrite
7091 existing torrc files.
7092 - Make OS X log happily to /var/log/tor/tor.log
7095 Changes in version 0.0.9.5 - 2005-02-22
7096 o Bugfixes on 0.0.9.x:
7097 - Fix an assert race at exit nodes when resolve requests fail.
7098 - Stop picking unverified dir mirrors--it only leads to misery.
7099 - Patch from Matt Edman to make NT services work better. Service
7100 support is still not compiled into the executable by default.
7101 - Patch from Dmitri Bely so the Tor service runs better under
7102 the win32 SYSTEM account.
7103 - Make tor-resolve actually work (?) on Win32.
7104 - Fix a sign bug when getrlimit claims to have 4+ billion
7105 file descriptors available.
7106 - Stop refusing to start when bandwidthburst == bandwidthrate.
7107 - When create cells have been on the onion queue more than five
7108 seconds, just send back a destroy and take them off the list.
7111 Changes in version 0.0.9.4 - 2005-02-03
7112 o Bugfixes on 0.0.9:
7113 - Fix an assert bug that took down most of our servers: when
7114 a server claims to have 1 GB of bandwidthburst, don't
7116 - Don't crash as badly if we have spawned the max allowed number
7117 of dnsworkers, or we're out of file descriptors.
7118 - Block more file-sharing ports in the default exit policy.
7119 - MaxConn is now automatically set to the hard limit of max
7120 file descriptors we're allowed (ulimit -n), minus a few for
7122 - Give a clearer message when servers need to raise their
7123 ulimit -n when they start running out of file descriptors.
7124 - SGI Compatibility patches from Jan Schaumann.
7125 - Tolerate a corrupt cached directory better.
7126 - When a dirserver hasn't approved your server, list which one.
7127 - Go into soft hibernation after 95% of the bandwidth is used,
7128 not 99%. This is especially important for daily hibernators who
7129 have a small accounting max. Hopefully it will result in fewer
7130 cut connections when the hard hibernation starts.
7131 - Load-balance better when using servers that claim more than
7132 800kB/s of capacity.
7133 - Make NT services work (experimental, only used if compiled in).
7136 Changes in version 0.0.9.3 - 2005-01-21
7137 o Bugfixes on 0.0.9:
7138 - Backport the cpu use fixes from main branch, so busy servers won't
7139 need as much processor time.
7140 - Work better when we go offline and then come back, or when we
7141 run Tor at boot before the network is up. We do this by
7142 optimistically trying to fetch a new directory whenever an
7143 application request comes in and we think we're offline -- the
7144 human is hopefully a good measure of when the network is back.
7145 - Backport some minimal hidserv bugfixes: keep rend circuits open as
7146 long as you keep using them; actually publish hidserv descriptors
7147 shortly after they change, rather than waiting 20-40 minutes.
7148 - Enable Mac startup script by default.
7149 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
7150 - When you update AllowUnverifiedNodes or FirewallPorts via the
7151 controller's setconf feature, we were always appending, never
7153 - When you update HiddenServiceDir via setconf, it was screwing up
7154 the order of reading the lines, making it fail.
7155 - Do not rewrite a cached directory back to the cache; otherwise we
7156 will think it is recent and not fetch a newer one on startup.
7157 - Workaround for webservers that lie about Content-Encoding: Tor
7158 now tries to autodetect compressed directories and compression
7159 itself. This lets us Proxypass dir fetches through apache.
7162 Changes in version 0.0.9.2 - 2005-01-04
7163 o Bugfixes on 0.0.9 (crashes and asserts):
7164 - Fix an assert on startup when the disk is full and you're logging
7166 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
7167 style address, then we'd crash.
7168 - Fix an assert trigger when the running-routers string we get from
7169 a dirserver is broken.
7170 - Make worker threads start and run on win32. Now win32 servers
7172 - Bandaid (not actually fix, but now it doesn't crash) an assert
7173 where the dns worker dies mysteriously and the main Tor process
7174 doesn't remember anything about the address it was resolving.
7176 o Bugfixes on 0.0.9 (Win32):
7177 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
7178 name out of the warning/assert messages.
7179 - Fix a superficial "unhandled error on read" bug on win32.
7180 - The win32 installer no longer requires a click-through for our
7181 license, since our Free Software license grants rights but does not
7183 - Win32: When connecting to a dirserver fails, try another one
7184 immediately. (This was already working for non-win32 Tors.)
7185 - Stop trying to parse $HOME on win32 when hunting for default
7187 - Make tor-resolve.c work on win32 by calling network_init().
7189 o Bugfixes on 0.0.9 (other):
7190 - Make 0.0.9.x build on Solaris again.
7191 - Due to a fencepost error, we were blowing away the \n when reporting
7192 confvalue items in the controller. So asking for multiple config
7193 values at once couldn't work.
7194 - When listing circuits that are pending on an opening OR connection,
7195 if we're an OR we were listing circuits that *end* at us as
7196 being pending on every listener, dns/cpu worker, etc. Stop that.
7197 - Dirservers were failing to create 'running-routers' or 'directory'
7198 strings if we had more than some threshold of routers. Fix them so
7199 they can handle any number of routers.
7200 - Fix a superficial "Duplicate mark for close" bug.
7201 - Stop checking for clock skew for OR connections, even for servers.
7202 - Fix a fencepost error that was chopping off the last letter of any
7203 nickname that is the maximum allowed nickname length.
7204 - Update URLs in log messages so they point to the new website.
7205 - Fix a potential problem in mangling server private keys while
7206 writing to disk (not triggered yet, as far as we know).
7207 - Include the licenses for other free software we include in Tor,
7208 now that we're shipping binary distributions more regularly.
7211 Changes in version 0.0.9.1 - 2004-12-15
7212 o Bugfixes on 0.0.9:
7213 - Make hibernation actually work.
7214 - Make HashedControlPassword config option work.
7215 - When we're reporting event circuit status to a controller,
7216 don't use the stream status code.
7219 Changes in version 0.0.9 - 2004-12-12
7220 o Bugfixes on 0.0.8.1 (Crashes and asserts):
7221 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
7222 write() call will fail and we handle it there.
7223 - When we run out of disk space, or other log writing error, don't
7224 crash. Just stop logging to that log and continue.
7225 - Fix isspace() and friends so they still make Solaris happy
7226 but also so they don't trigger asserts on win32.
7227 - Fix assert failure on malformed socks4a requests.
7228 - Fix an assert bug where a hidden service provider would fail if
7229 the first hop of his rendezvous circuit was down.
7230 - Better handling of size_t vs int, so we're more robust on 64
7233 o Bugfixes on 0.0.8.1 (Win32):
7234 - Make windows sockets actually non-blocking (oops), and handle
7235 win32 socket errors better.
7236 - Fix parse_iso_time on platforms without strptime (eg win32).
7237 - win32: when being multithreaded, leave parent fdarray open.
7238 - Better handling of winsock includes on non-MSV win32 compilers.
7239 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
7241 - Make unit tests work on win32.
7243 o Bugfixes on 0.0.8.1 (Path selection and streams):
7244 - Calculate timeout for waiting for a connected cell from the time
7245 we sent the begin cell, not from the time the stream started. If
7246 it took a long time to establish the circuit, we would time out
7247 right after sending the begin cell.
7248 - Fix router_compare_addr_to_addr_policy: it was not treating a port
7249 of * as always matching, so we were picking reject *:* nodes as
7250 exit nodes too. Oops.
7251 - When read() failed on a stream, we would close it without sending
7252 back an end. So 'connection refused' would simply be ignored and
7253 the user would get no response.
7254 - Stop a sigpipe: when an 'end' cell races with eof from the app,
7255 we shouldn't hold-open-until-flush if the eof arrived first.
7256 - Let resolve conns retry/expire also, rather than sticking around
7258 - Fix more dns related bugs: send back resolve_failed and end cells
7259 more reliably when the resolve fails, rather than closing the
7260 circuit and then trying to send the cell. Also attach dummy resolve
7261 connections to a circuit *before* calling dns_resolve(), to fix
7262 a bug where cached answers would never be sent in RESOLVED cells.
7264 o Bugfixes on 0.0.8.1 (Circuits):
7265 - Finally fix a bug that's been plaguing us for a year:
7266 With high load, circuit package window was reaching 0. Whenever
7267 we got a circuit-level sendme, we were reading a lot on each
7268 socket, but only writing out a bit. So we would eventually reach
7269 eof. This would be noticed and acted on even when there were still
7270 bytes sitting in the inbuf.
7271 - Use identity comparison, not nickname comparison, to choose which
7272 half of circuit-ID-space each side gets to use. This is needed
7273 because sometimes we think of a router as a nickname, and sometimes
7274 as a hex ID, and we can't predict what the other side will do.
7276 o Bugfixes on 0.0.8.1 (Other):
7277 - Fix a whole slew of memory leaks.
7278 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
7279 - If we are using select, make sure we stay within FD_SETSIZE.
7280 - When poll() is interrupted, we shouldn't believe the revents values.
7281 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
7282 and smartlist_len, which are two major profiling offenders.
7283 - If do_hup fails, actually notice.
7284 - Flush the log file descriptor after we print "Tor opening log file",
7285 so we don't see those messages days later.
7286 - Hidden service operators now correctly handle version 1 style
7287 INTRODUCE1 cells (nobody generates them still, so not a critical
7289 - Handle more errnos from accept() without closing the listener.
7290 Some OpenBSD machines were closing their listeners because
7291 they ran out of file descriptors.
7292 - Some people had wrapped their tor client/server in a script
7293 that would restart it whenever it died. This did not play well
7294 with our "shut down if your version is obsolete" code. Now people
7295 don't fetch a new directory if their local cached version is
7297 - Make our autogen.sh work on ksh as well as bash.
7298 - Better torrc example lines for dirbindaddress and orbindaddress.
7299 - Improved bounds checking on parsed ints (e.g. config options and
7300 the ones we find in directories.)
7301 - Stop using separate defaults for no-config-file and
7302 empty-config-file. Now you have to explicitly turn off SocksPort,
7303 if you don't want it open.
7304 - We were starting to daemonize before we opened our logs, so if
7305 there were any problems opening logs, we would complain to stderr,
7306 which wouldn't work, and then mysteriously exit.
7307 - If a verified OR connects to us before he's uploaded his descriptor,
7308 or we verify him and hup but he still has the original TLS
7309 connection, then conn->nickname is still set like he's unverified.
7311 o Code security improvements, inspired by Ilja:
7312 - tor_snprintf wrapper over snprintf with consistent (though not C99)
7314 - Replace sprintf with tor_snprintf. (I think they were all safe, but
7316 - Replace strcpy/strncpy with strlcpy in more places.
7317 - Avoid strcat; use tor_snprintf or strlcat instead.
7319 o Features (circuits and streams):
7320 - New circuit building strategy: keep a list of ports that we've
7321 used in the past 6 hours, and always try to have 2 circuits open
7322 or on the way that will handle each such port. Seed us with port
7323 80 so web users won't complain that Tor is "slow to start up".
7324 - Make kill -USR1 dump more useful stats about circuits.
7325 - When warning about retrying or giving up, print the address, so
7326 the user knows which one it's talking about.
7327 - If you haven't used a clean circuit in an hour, throw it away,
7328 just to be on the safe side. (This means after 6 hours a totally
7329 unused Tor client will have no circuits open.)
7330 - Support "foo.nickname.exit" addresses, to let Alice request the
7331 address "foo" as viewed by exit node "nickname". Based on a patch
7333 - If your requested entry or exit node has advertised bandwidth 0,
7335 - Be more greedy about filling up relay cells -- we try reading again
7336 once we've processed the stuff we read, in case enough has arrived
7337 to fill the last cell completely.
7338 - Refuse application socks connections to port 0.
7339 - Use only 0.0.9pre1 and later servers for resolve cells.
7341 o Features (bandwidth):
7342 - Hibernation: New config option "AccountingMax" lets you
7343 set how many bytes per month (in each direction) you want to
7344 allow your server to consume. Rather than spreading those
7345 bytes out evenly over the month, we instead hibernate for some
7346 of the month and pop up at a deterministic time, work until
7347 the bytes are consumed, then hibernate again. Config option
7348 "MonthlyAccountingStart" lets you specify which day of the month
7349 your billing cycle starts on.
7350 - Implement weekly/monthly/daily accounting: now you specify your
7351 hibernation properties by
7352 AccountingMax N bytes|KB|MB|GB|TB
7353 AccountingStart day|week|month [day] HH:MM
7354 Defaults to "month 1 0:00".
7355 - Let bandwidth and interval config options be specified as 5 bytes,
7356 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
7358 o Features (directories):
7359 - New "router-status" line in directory, to better bind each verified
7360 nickname to its identity key.
7361 - Clients can ask dirservers for /dir.z to get a compressed version
7362 of the directory. Only works for servers running 0.0.9, of course.
7363 - Make clients cache directories and use them to seed their router
7364 lists at startup. This means clients have a datadir again.
7365 - Respond to content-encoding headers by trying to uncompress as
7367 - Clients and servers now fetch running-routers; cache
7368 running-routers; compress running-routers; serve compressed
7370 - Make moria2 advertise a dirport of 80, so people behind firewalls
7371 will be able to get a directory.
7372 - Http proxy support
7373 - Dirservers translate requests for http://%s:%d/x to /x
7374 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
7375 be routed through this host.
7376 - Clients ask for /tor/x rather than /x for new enough dirservers.
7377 This way we can one day coexist peacefully with apache.
7378 - Clients specify a "Host: %s%d" http header, to be compatible
7379 with more proxies, and so running squid on an exit node can work.
7380 - Protect dirservers from overzealous descriptor uploading -- wait
7381 10 seconds after directory gets dirty, before regenerating.
7383 o Features (packages and install):
7384 - Add NSI installer contributed by J Doe.
7385 - Apply NT service patch from Osamu Fujino. Still needs more work.
7386 - Commit VC6 and VC7 workspace/project files.
7387 - Commit a tor.spec for making RPM files, with help from jbash.
7388 - Add contrib/torctl.in contributed by Glenn Fink.
7389 - Make expand_filename handle ~ and ~username.
7390 - Use autoconf to enable largefile support where necessary. Use
7391 ftello where available, since ftell can fail at 2GB.
7392 - Ship src/win32/ in the tarball, so people can use it to build.
7393 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
7396 o Features (ui controller):
7397 - Control interface: a separate program can now talk to your
7398 client/server over a socket, and get/set config options, receive
7399 notifications of circuits and streams starting/finishing/dying,
7400 bandwidth used, etc. The next step is to get some GUIs working.
7401 Let us know if you want to help out. See doc/control-spec.txt .
7402 - Ship a contrib/tor-control.py as an example script to interact
7403 with the control port.
7404 - "tor --hash-password zzyxz" will output a salted password for
7405 use in authenticating to the control interface.
7406 - Implement the control-spec's SAVECONF command, to write your
7407 configuration to torrc.
7408 - Get cookie authentication for the controller closer to working.
7409 - When set_conf changes our server descriptor, upload a new copy.
7410 But don't upload it too often if there are frequent changes.
7412 o Features (config and command-line):
7413 - Deprecate unofficial config option abbreviations, and abbreviations
7414 not on the command line.
7415 - Configuration infrastructure support for warning on obsolete
7417 - Give a slightly more useful output for "tor -h".
7418 - Break DirFetchPostPeriod into:
7419 - DirFetchPeriod for fetching full directory,
7420 - StatusFetchPeriod for fetching running-routers,
7421 - DirPostPeriod for posting server descriptor,
7422 - RendPostPeriod for posting hidden service descriptors.
7423 - New log format in config:
7424 "Log minsev[-maxsev] stdout|stderr|syslog" or
7425 "Log minsev[-maxsev] file /var/foo"
7426 - DirPolicy config option, to let people reject incoming addresses
7427 from their dirserver.
7428 - "tor --list-fingerprint" will list your identity key fingerprint
7430 - Make tor --version --version dump the cvs Id of every file.
7431 - New 'MyFamily nick1,...' config option for a server to
7432 specify other servers that shouldn't be used in the same circuit
7433 with it. Only believed if nick1 also specifies us.
7434 - New 'NodeFamily nick1,nick2,...' config option for a client to
7435 specify nodes that it doesn't want to use in the same circuit.
7436 - New 'Redirectexit pattern address:port' config option for a
7437 server to redirect exit connections, e.g. to a local squid.
7438 - Add "pass" target for RedirectExit, to make it easier to break
7439 out of a sequence of RedirectExit rules.
7440 - Make the dirservers file obsolete.
7441 - Include a dir-signing-key token in directories to tell the
7442 parsing entity which key is being used to sign.
7443 - Remove the built-in bulky default dirservers string.
7444 - New config option "Dirserver %s:%d [fingerprint]", which can be
7445 repeated as many times as needed. If no dirservers specified,
7446 default to moria1,moria2,tor26.
7447 - Make 'Routerfile' config option obsolete.
7448 - Discourage people from setting their dirfetchpostperiod more often
7449 than once per minute.
7452 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
7453 get back to normal.)
7454 - Accept *:706 (silc) in default exit policy.
7455 - Implement new versioning format for post 0.1.
7456 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
7457 log more informatively.
7458 - Check clock skew for verified servers, but allow unverified
7459 servers and clients to have any clock skew.
7460 - Make sure the hidden service descriptors are at a random offset
7461 from each other, to hinder linkability.
7462 - Clients now generate a TLS cert too, in preparation for having
7463 them act more like real nodes.
7464 - Add a pure-C tor-resolve implementation.
7465 - Use getrlimit and friends to ensure we can reach MaxConn (currently
7466 1024) file descriptors.
7467 - Raise the max dns workers from 50 to 100.
7470 Changes in version 0.0.8.1 - 2004-10-13
7472 - Fix a seg fault that can be triggered remotely for Tor
7473 clients/servers with an open dirport.
7474 - Fix a rare assert trigger, where routerinfos for entries in
7475 our cpath would expire while we're building the path.
7476 - Fix a bug in OutboundBindAddress so it (hopefully) works.
7477 - Fix a rare seg fault for people running hidden services on
7478 intermittent connections.
7479 - Fix a bug in parsing opt keywords with objects.
7480 - Fix a stale pointer assert bug when a stream detaches and
7482 - Fix a string format vulnerability (probably not exploitable)
7483 in reporting stats locally.
7484 - Fix an assert trigger: sometimes launching circuits can fail
7485 immediately, e.g. because too many circuits have failed recently.
7486 - Fix a compile warning on 64 bit platforms.
7489 Changes in version 0.0.8 - 2004-08-25
7491 - Made our unit tests compile again on OpenBSD 3.5, and tor
7492 itself compile again on OpenBSD on a sparc64.
7493 - We were neglecting milliseconds when logging on win32, so
7494 everything appeared to happen at the beginning of each second.
7495 - Check directory signature _before_ you decide whether you're
7496 you're running an obsolete version and should exit.
7497 - Check directory signature _before_ you parse the running-routers
7498 list to decide who's running.
7499 - Check return value of fclose while writing to disk, so we don't
7500 end up with broken files when servers run out of disk space.
7501 - Port it to SunOS 5.9 / Athena
7502 - Fix two bugs in saving onion keys to disk when rotating, so
7503 hopefully we'll get fewer people using old onion keys.
7504 - Remove our mostly unused -- and broken -- hex_encode()
7505 function. Use base16_encode() instead. (Thanks to Timo Lindfors
7506 for pointing out this bug.)
7507 - Only pick and establish intro points after we've gotten a
7509 - Fix assert triggers: if the other side returns an address 0.0.0.0,
7510 don't put it into the client dns cache.
7511 - If a begin failed due to exit policy, but we believe the IP
7512 address should have been allowed, switch that router to exitpolicy
7513 reject *:* until we get our next directory.
7516 - 'Extend' relay cell payloads now include the digest of the
7517 intended next hop's identity key. Now we can verify that we're
7518 extending to the right router, and also extend to routers we
7519 hadn't heard of before.
7522 - Tor nodes can now act as relays (with an advertised ORPort)
7523 without being manually verified by the dirserver operators.
7524 - Uploaded descriptors of unverified routers are now accepted
7525 by the dirservers, and included in the directory.
7526 - Verified routers are listed by nickname in the running-routers
7527 list; unverified routers are listed as "$<fingerprint>".
7528 - We now use hash-of-identity-key in most places rather than
7529 nickname or addr:port, for improved security/flexibility.
7530 - AllowUnverifiedNodes config option to let circuits choose no-name
7531 routers in entry,middle,exit,introduction,rendezvous positions.
7532 Allow middle and rendezvous positions by default.
7533 - When picking unverified routers, skip those with low uptime and/or
7534 low bandwidth, depending on what properties you care about.
7535 - ClientOnly option for nodes that never want to become servers.
7536 - Directory caching.
7537 - "AuthoritativeDir 1" option for the official dirservers.
7538 - Now other nodes (clients and servers) will cache the latest
7539 directory they've pulled down.
7540 - They can enable their DirPort to serve it to others.
7541 - Clients will pull down a directory from any node with an open
7542 DirPort, and check the signature/timestamp correctly.
7543 - Authoritative dirservers now fetch directories from other
7544 authdirservers, to stay better synced.
7545 - Running-routers list tells who's down also, along with noting
7546 if they're verified (listed by nickname) or unverified (listed
7548 - Allow dirservers to serve running-router list separately.
7549 This isn't used yet.
7550 - You can now fetch $DIRURL/running-routers to get just the
7551 running-routers line, not the whole descriptor list. (But
7552 clients don't use this yet.)
7553 - Clients choose nodes proportional to advertised bandwidth.
7554 - Clients avoid using nodes with low uptime as introduction points.
7555 - Handle servers with dynamic IP addresses: don't just replace
7556 options->Address with the resolved one at startup, and
7557 detect our address right before we make a routerinfo each time.
7558 - 'FascistFirewall' option to pick dirservers and ORs on specific
7559 ports; plus 'FirewallPorts' config option to tell FascistFirewall
7560 which ports are open. (Defaults to 80,443)
7561 - Try other dirservers immediately if the one you try is down. This
7562 should tolerate down dirservers better now.
7563 - ORs connect-on-demand to other ORs
7564 - If you get an extend cell to an OR you're not connected to,
7565 connect, handshake, and forward the create cell.
7566 - The authoritative dirservers stay connected to everybody,
7567 and everybody stays connected to 0.0.7 servers, but otherwise
7568 clients/servers expire unused connections after 5 minutes.
7569 - When servers get a sigint, they delay 30 seconds (refusing new
7570 connections) then exit. A second sigint causes immediate exit.
7571 - File and name management:
7572 - Look for .torrc if no CONFDIR "torrc" is found.
7573 - If no datadir is defined, then choose, make, and secure ~/.tor
7575 - If torrc not found, exitpolicy reject *:*.
7576 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
7577 - If no nickname is defined, derive default from hostname.
7578 - Rename secret key files, e.g. identity.key -> secret_id_key,
7579 to discourage people from mailing their identity key to tor-ops.
7580 - Refuse to build a circuit before the directory has arrived --
7581 it won't work anyway, since you won't know the right onion keys
7583 - Parse tor version numbers so we can do an is-newer-than check
7584 rather than an is-in-the-list check.
7585 - New socks command 'resolve', to let us shim gethostbyname()
7587 - A 'tor_resolve' script to access the socks resolve functionality.
7588 - A new socks-extensions.txt doc file to describe our
7589 interpretation and extensions to the socks protocols.
7590 - Add a ContactInfo option, which gets published in descriptor.
7591 - Write tor version at the top of each log file
7592 - New docs in the tarball:
7594 - Document that you should proxy your SSL traffic too.
7595 - Log a warning if the user uses an unsafe socks variant, so people
7596 are more likely to learn about privoxy or socat.
7597 - Log a warning if you're running an unverified server, to let you
7598 know you might want to get it verified.
7599 - Change the default exit policy to reject the default edonkey,
7600 kazaa, gnutella ports.
7601 - Add replace_file() to util.[ch] to handle win32's rename().
7602 - Publish OR uptime in descriptor (and thus in directory) too.
7603 - Remember used bandwidth (both in and out), and publish 15-minute
7604 snapshots for the past day into our descriptor.
7605 - Be more aggressive about trying to make circuits when the network
7606 has changed (e.g. when you unsuspend your laptop).
7607 - Check for time skew on http headers; report date in response to
7609 - If the entrynode config line has only one node, don't pick it as
7611 - Add strict{entry|exit}nodes config options. If set to 1, then
7612 we refuse to build circuits that don't include the specified entry
7614 - OutboundBindAddress config option, to bind to a specific
7615 IP address for outgoing connect()s.
7616 - End truncated log entries (e.g. directories) with "[truncated]".
7619 Changes in version 0.0.7.3 - 2004-08-12
7620 o Stop dnsworkers from triggering an assert failure when you
7621 ask them to resolve the host "".
7624 Changes in version 0.0.7.2 - 2004-07-07
7625 o A better fix for the 0.0.0.0 problem, that will hopefully
7626 eliminate the remaining related assertion failures.
7629 Changes in version 0.0.7.1 - 2004-07-04
7630 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
7631 since internally we use 0.0.0.0 to signify "not yet resolved".
7634 Changes in version 0.0.7 - 2004-06-07
7635 o Fixes for crashes and other obnoxious bugs:
7636 - Fix an epipe bug: sometimes when directory connections failed
7637 to connect, we would give them a chance to flush before closing
7639 - When we detached from a circuit because of resolvefailed, we
7640 would immediately try the same circuit twice more, and then
7641 give up on the resolve thinking we'd tried three different
7643 - Limit the number of intro circuits we'll attempt to build for a
7644 hidden service per 15-minute period.
7645 - Check recommended-software string *early*, before actually parsing
7646 the directory. Thus we can detect an obsolete version and exit,
7647 even if the new directory format doesn't parse.
7648 o Fixes for security bugs:
7649 - Remember which nodes are dirservers when you startup, and if a
7650 random OR enables his dirport, don't automatically assume he's
7651 a trusted dirserver.
7653 - Directory connections were asking the wrong poll socket to
7654 start writing, and not asking themselves to start writing.
7655 - When we detached from a circuit because we sent a begin but
7656 didn't get a connected, we would use it again the first time;
7657 but after that we would correctly switch to a different one.
7658 - Stop warning when the first onion decrypt attempt fails; they
7659 will sometimes legitimately fail now that we rotate keys.
7660 - Override unaligned-access-ok check when $host_cpu is ia64 or
7661 arm. Apparently they allow it but the kernel whines.
7662 - Dirservers try to reconnect periodically too, in case connections
7664 - Fix some memory leaks in directory servers.
7665 - Allow backslash in Win32 filenames.
7666 - Made Tor build complain-free on FreeBSD, hopefully without
7667 breaking other BSD builds. We'll see.
7668 - Check directory signatures based on name of signer, not on whom
7669 we got the directory from. This will let us cache directories more
7671 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
7674 - Doxygen markup on all functions and global variables.
7675 - Make directory functions update routerlist, not replace it. So
7676 now directory disagreements are not so critical a problem.
7677 - Remove the upper limit on number of descriptors in a dirserver's
7678 directory (not that we were anywhere close).
7679 - Allow multiple logfiles at different severity ranges.
7680 - Allow *BindAddress to specify ":port" rather than setting *Port
7681 separately. Allow multiple instances of each BindAddress config
7682 option, so you can bind to multiple interfaces if you want.
7683 - Allow multiple exit policy lines, which are processed in order.
7684 Now we don't need that huge line with all the commas in it.
7685 - Enable accept/reject policies on SOCKS connections, so you can bind
7686 to 0.0.0.0 but still control who can use your OP.
7687 - Updated the man page to reflect these features.
7690 Changes in version 0.0.6.2 - 2004-05-16
7691 o Our integrity-checking digest was checking only the most recent cell,
7692 not the previous cells like we'd thought.
7693 Thanks to Stefan Mark for finding the flaw!
7696 Changes in version 0.0.6.1 - 2004-05-06
7697 o Fix two bugs in our AES counter-mode implementation (this affected
7698 onion-level stream encryption, but not TLS-level). It turns
7699 out we were doing something much more akin to a 16-character
7700 polyalphabetic cipher. Oops.
7701 Thanks to Stefan Mark for finding the flaw!
7702 o Retire moria3 as a directory server, and add tor26 as a directory
7706 Changes in version 0.0.6 - 2004-05-02
7708 - Hidden services and rendezvous points are implemented. Go to
7709 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
7710 hidden services. (This only works via a socks4a proxy such as
7711 Privoxy, and currently it's quite slow.)
7712 - We now rotate link (tls context) keys and onion keys.
7713 - CREATE cells now include oaep padding, so you can tell
7714 if you decrypted them correctly.
7715 - Retry stream correctly when we fail to connect because of
7716 exit-policy-reject (should try another) or can't-resolve-address.
7717 - When we hup a dirserver and we've *removed* a server from the
7718 approved-routers list, now we remove that server from the
7719 in-memory directories too.
7720 - Add bandwidthburst to server descriptor.
7721 - Directories now say which dirserver signed them.
7722 - Use a tor_assert macro that logs failed assertions too.
7723 - Since we don't support truncateds much, don't bother sending them;
7724 just close the circ.
7725 - Fetch randomness from /dev/urandom better (not via fopen/fread)
7726 - Better debugging for tls errors
7727 - Set Content-Type on the directory and hidserv descriptor.
7728 - Remove IVs from cipher code, since AES-ctr has none.
7730 - Fix an assert trigger for exit nodes that's been plaguing us since
7731 the days of 0.0.2prexx (thanks weasel!)
7732 - Fix a bug where we were closing tls connections intermittently.
7733 It turns out openssl keeps its errors around -- so if an error
7734 happens, and you don't ask about it, and then another openssl
7735 operation happens and succeeds, and you ask if there was an error,
7736 it tells you about the first error.
7737 - Fix a bug that's been lurking since 27 may 03 (!)
7738 When passing back a destroy cell, we would use the wrong circ id.
7739 - Don't crash if a conn that sent a begin has suddenly lost its circuit.
7740 - Some versions of openssl have an SSL_pending function that erroneously
7741 returns bytes when there is a non-application record pending.
7742 - Win32 fixes. Tor now compiles on win32 with no warnings/errors.
7743 o We were using an array of length zero in a few places.
7744 o Win32's gethostbyname can't resolve an IP to an IP.
7745 o Win32's close can't close a socket.
7746 o Handle windows socket errors correctly.
7748 - check for <sys/limits.h> so we build on FreeBSD again, and
7749 <machine/limits.h> for NetBSD.
7752 Changes in version 0.0.5 - 2004-03-30
7753 o Install torrc as torrc.sample -- we no longer clobber your
7755 o Fix mangled-state bug in directory fetching (was causing sigpipes).
7756 o Only build circuits after we've fetched the directory: clients were
7757 using only the directory servers before they'd fetched a directory.
7758 This also means longer startup time; so it goes.
7759 o Fix an assert trigger where an OP would fail to handshake, and we'd
7760 expect it to have a nickname.
7761 o Work around a tsocks bug: do a socks reject when AP connection dies
7762 early, else tsocks goes into an infinite loop.
7763 o Hold socks connection open until reply is flushed (if possible)
7764 o Make exit nodes resolve IPs to IPs immediately, rather than asking
7765 the dns farm to do it.
7766 o Fix c99 aliasing warnings in rephist.c
7767 o Don't include server descriptors that are older than 24 hours in the
7769 o Give socks 'reject' replies their whole 15s to attempt to flush,
7770 rather than seeing the 60s timeout and assuming the flush had failed.
7771 o Clean automake droppings from the cvs repository
7772 o Add in a 'notice' log level for things the operator should hear
7773 but that aren't warnings
7776 Changes in version 0.0.4 - 2004-03-26
7777 o When connecting to a dirserver or OR and the network is down,
7781 Changes in version 0.0.3 - 2004-03-26
7782 o Warn and fail if server chose a nickname with illegal characters
7783 o Port to Solaris and Sparc:
7784 - include missing header fcntl.h
7785 - have autoconf find -lsocket -lnsl automatically
7786 - deal with hardware word alignment
7787 - make uname() work (solaris has a different return convention)
7788 - switch from using signal() to sigaction()
7789 o Preliminary work on reputation system:
7790 - Keep statistics on success/fail of connect attempts; they're published
7791 by kill -USR1 currently.
7792 - Add a RunTesting option to try to learn link state by creating test
7793 circuits, even when SocksPort is off.
7794 - Remove unused open circuits when there are too many.
7797 Changes in version 0.0.2 - 2004-03-19
7798 - Include strlcpy and strlcat for safer string ops
7799 - define INADDR_NONE so we compile (but still not run) on solaris
7802 Changes in version 0.0.2pre27 - 2004-03-14
7804 - Allow internal tor networks (we were rejecting internal IPs,
7805 now we allow them if they're set explicitly).
7806 - And fix a few endian issues.
7809 Changes in version 0.0.2pre26 - 2004-03-14
7811 - If a stream times out after 15s without a connected cell, don't
7812 try that circuit again: try a new one.
7813 - Retry streams at most 4 times. Then give up.
7814 - When a dirserver gets a descriptor from an unknown router, it
7815 logs its fingerprint (so the dirserver operator can choose to
7816 accept it even without mail from the server operator).
7817 - Inform unapproved servers when we reject their descriptors.
7818 - Make tor build on Windows again. It works as a client, who knows
7820 - Clearer instructions in the torrc for how to set up a server.
7821 - Be more efficient about reading fd's when our global token bucket
7822 (used for rate limiting) becomes empty.
7824 - Stop asserting that computers always go forward in time. It's
7826 - When we sent a cell (e.g. destroy) and then marked an OR connection
7827 expired, we might close it before finishing a flush if the other
7828 side isn't reading right then.
7829 - Don't allow dirservers to start if they haven't defined
7831 - We were caching transient dns failures. Oops.
7832 - Prevent servers from publishing an internal IP as their address.
7833 - Address a strcat vulnerability in circuit.c
7836 Changes in version 0.0.2pre25 - 2004-03-04
7838 - Put the OR's IP in its router descriptor, not its fqdn. That way
7839 we'll stop being stalled by gethostbyname for nodes with flaky dns,
7842 - If the user typed in an address that didn't resolve, the server
7846 Changes in version 0.0.2pre24 - 2004-03-03
7848 - Fix an assertion failure in dns.c, where we were trying to dequeue
7849 a pending dns resolve even if it wasn't pending
7850 - Fix a spurious socks5 warning about still trying to write after the
7851 connection is finished.
7852 - Hold certain marked_for_close connections open until they're finished
7853 flushing, rather than losing bytes by closing them too early.
7854 - Correctly report the reason for ending a stream
7855 - Remove some duplicate calls to connection_mark_for_close
7856 - Put switch_id and start_daemon earlier in the boot sequence, so it
7857 will actually try to chdir() to options.DataDirectory
7858 - Make 'make test' exit(1) if a test fails; fix some unit tests
7859 - Make tor fail when you use a config option it doesn't know about,
7860 rather than warn and continue.
7861 - Make --version work
7862 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
7865 Changes in version 0.0.2pre23 - 2004-02-29
7867 - Print a statement when the first circ is finished, so the user
7869 - If a relay cell is unrecognized at the end of the circuit,
7870 send back a destroy. (So attacks to mutate cells are more
7872 - New config option 'excludenodes' to avoid certain nodes for circuits.
7873 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
7874 so you can collect coredumps there.
7876 - Fix a bug in tls flushing where sometimes data got wedged and
7877 didn't flush until more data got sent. Hopefully this bug was
7878 a big factor in the random delays we were seeing.
7879 - Make 'connected' cells include the resolved IP, so the client
7880 dns cache actually gets populated.
7881 - Disallow changing from ORPort=0 to ORPort>0 on hup.
7882 - When we time-out on a stream and detach from the circuit, send an
7883 end cell down it first.
7884 - Only warn about an unknown router (in exitnodes, entrynodes,
7885 excludenodes) after we've fetched a directory.
7888 Changes in version 0.0.2pre22 - 2004-02-26
7890 - Servers publish less revealing uname information in descriptors.
7891 - More memory tracking and assertions, to crash more usefully when
7893 - If the default torrc isn't there, just use some default defaults.
7894 Plus provide an internal dirservers file if they don't have one.
7895 - When the user tries to use Tor as an http proxy, give them an http
7896 501 failure explaining that we're a socks proxy.
7897 - Dump a new router.desc on hup, to help confused people who change
7898 their exit policies and then wonder why router.desc doesn't reflect
7900 - Clean up the generic tor.sh init script that we ship with.
7902 - If the exit stream is pending on the resolve, and a destroy arrives,
7903 then the stream wasn't getting removed from the pending list. I
7904 think this was the one causing recent server crashes.
7905 - Use a more robust poll on OSX 10.3, since their poll is flaky.
7906 - When it couldn't resolve any dirservers, it was useless from then on.
7907 Now it reloads the RouterFile (or default dirservers) if it has no
7909 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
7910 many users don't even *have* a /usr/local/sbin/.
7913 Changes in version 0.0.2pre21 - 2004-02-18
7915 - There's a ChangeLog file that actually reflects the changelog.
7916 - There's a 'torify' wrapper script, with an accompanying
7917 tor-tsocks.conf, that simplifies the process of using tsocks for
7918 tor. It even has a man page.
7919 - The tor binary gets installed to sbin rather than bin now.
7920 - Retry streams where the connected cell hasn't arrived in 15 seconds
7921 - Clean up exit policy handling -- get the default out of the torrc,
7922 so we can update it without forcing each server operator to fix
7924 - Allow imaps and pop3s in default exit policy
7926 - Prevent picking middleman nodes as the last node in the circuit
7929 Changes in version 0.0.2pre20 - 2004-01-30
7931 - We now have a deb package, and it's in debian unstable. Go to
7933 - I've split the TotalBandwidth option into BandwidthRate (how many
7934 bytes per second you want to allow, long-term) and
7935 BandwidthBurst (how many bytes you will allow at once before the cap
7936 kicks in). This better token bucket approach lets you, say, set
7937 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
7938 performance while not exceeding your monthly bandwidth quota.
7939 - Push out a tls record's worth of data once you've got it, rather
7940 than waiting until you've read everything waiting to be read. This
7941 may improve performance by pipelining better. We'll see.
7942 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
7943 from failed circuits (if they haven't been connected yet) and attach
7945 - Expire old streams that haven't managed to connect. Some day we'll
7946 have them reattach to new circuits instead.
7949 - Fix several memory leaks that were causing servers to become bloated
7951 - Fix a few very rare assert triggers. A few more remain.
7952 - Setuid to User _before_ complaining about running as root.
7955 Changes in version 0.0.2pre19 - 2004-01-07
7957 - Fix deadlock condition in dns farm. We were telling a child to die by
7958 closing the parent's file descriptor to him. But newer children were
7959 inheriting the open file descriptor from the parent, and since they
7960 weren't closing it, the socket never closed, so the child never read
7961 eof, so he never knew to exit. Similarly, dns workers were holding
7962 open other sockets, leading to all sorts of chaos.
7963 - New cleaner daemon() code for forking and backgrounding.
7964 - If you log to a file, it now prints an entry at the top of the
7965 logfile so you know it's working.
7966 - The onionskin challenge length was 30 bytes longer than necessary.
7967 - Started to patch up the spec so it's not quite so out of date.
7970 Changes in version 0.0.2pre18 - 2004-01-02
7972 - Fix endian issues with the 'integrity' field in the relay header.
7973 - Fix a potential bug where connections in state
7974 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
7977 Changes in version 0.0.2pre17 - 2003-12-30
7979 - Made --debuglogfile (or any second log file, actually) work.
7980 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
7981 adversary could force us into an infinite loop.
7984 - Each onionskin handshake now includes a hash of the computed key,
7985 to prove the server's identity and help perfect forward secrecy.
7986 - Changed cell size from 256 to 512 bytes (working toward compatibility
7988 - Changed cell length to 2 bytes, and moved it to the relay header.
7989 - Implemented end-to-end integrity checking for the payloads of
7991 - Separated streamid from 'recognized' (otherwise circuits will get
7992 messed up when we try to have streams exit from the middle). We
7993 use the integrity-checking to confirm that a cell is addressed to
7995 - Randomize the initial circid and streamid values, so an adversary who
7996 breaks into a node can't learn how many circuits or streams have
8000 Changes in version 0.0.2pre16 - 2003-12-14
8002 - Fixed a bug that made HUP trigger an assert
8003 - Fixed a bug where a circuit that immediately failed wasn't being
8004 counted as a failed circuit in counting retries.
8007 - Now we close the circuit when we get a truncated cell: otherwise we're
8008 open to an anonymity attack where a bad node in the path truncates
8009 the circuit and then we open streams at him.
8010 - Add port ranges to exit policies
8011 - Add a conservative default exit policy
8012 - Warn if you're running tor as root
8013 - on HUP, retry OR connections and close/rebind listeners
8014 - options.EntryNodes: try these nodes first when picking the first node
8015 - options.ExitNodes: if your best choices happen to include any of
8016 your preferred exit nodes, you choose among just those preferred
8018 - options.ExcludedNodes: nodes that are never picked in path building
8021 Changes in version 0.0.2pre15 - 2003-12-03
8022 o Robustness and bugfixes:
8023 - Sometimes clients would cache incorrect DNS resolves, which would
8024 really screw things up.
8025 - An OP that goes offline would slowly leak all its sockets and stop
8027 - A wide variety of bugfixes in exit node selection, exit policy
8028 handling, and processing pending streams when a new circuit is
8030 - Pick nodes for a path only from those the directory says are up
8031 - Choose randomly from all running dirservers, not always the first one
8032 - Increase allowed http header size for directory fetch.
8033 - Stop writing to stderr (if we're daemonized it will be closed).
8034 - Enable -g always, so cores will be more useful to me.
8035 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
8038 - Wrote a man page. It lists commonly used options.
8041 - Change default loglevel to warn.
8042 - Make PidFile default to null rather than littering in your CWD.
8043 - OnionRouter config option is now obsolete. Instead it just checks
8045 - Moved to a single unified torrc file for both clients and servers.
8048 Changes in version 0.0.2pre14 - 2003-11-29
8049 o Robustness and bugfixes:
8050 - Force the admin to make the DataDirectory himself
8051 - to get ownership/permissions right
8052 - so clients no longer make a DataDirectory and then never use it
8053 - fix bug where a client who was offline for 45 minutes would never
8054 pull down a directory again
8055 - fix (or at least hide really well) the dns assert bug that was
8056 causing server crashes
8057 - warnings and improved robustness wrt clockskew for certs
8058 - use the native daemon(3) to daemonize, when available
8059 - exit if bind() fails
8060 - exit if neither socksport nor orport is defined
8061 - include our own tor_timegm (Win32 doesn't have its own)
8062 - bugfix for win32 with lots of connections
8063 - fix minor bias in PRNG
8064 - make dirserver more robust to corrupt cached directory
8067 - Wrote the design document (woo)
8069 o Circuit building and exit policies:
8070 - Circuits no longer try to use nodes that the directory has told them
8072 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
8073 bitcounts (18.0.0.0/8).
8074 - Make AP connections standby for a circuit if no suitable circuit
8075 exists, rather than failing
8076 - Circuits choose exit node based on addr/port, exit policies, and
8077 which AP connections are standing by
8078 - Bump min pathlen from 2 to 3
8079 - Relay end cells have a payload to describe why the stream ended.
8080 - If the stream failed because of exit policy, try again with a new
8082 - Clients have a dns cache to remember resolved addresses.
8083 - Notice more quickly when we have no working circuits
8086 - APPort is now called SocksPort
8087 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
8089 - RecommendedVersions is now a config variable rather than
8090 hardcoded (for dirservers)
8091 - Reloads config on HUP
8092 - Usage info on -h or --help
8093 - If you set User and Group config vars, it'll setu/gid to them.
8095 Changes in version 0.0.2pre13 - 2003-10-19
8096 o General stability:
8097 - SSL_write no longer fails when it returns WANTWRITE and the number
8098 of bytes in the buf has changed by the next SSL_write call.
8099 - Fix segfault fetching directory when network is down
8100 - Fix a variety of minor memory leaks
8101 - Dirservers reload the fingerprints file on HUP, so I don't have
8102 to take down the network when I approve a new router
8103 - Default server config file has explicit Address line to specify fqdn
8106 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
8107 - Make listener connections not ever alloc bufs
8109 o Autoconf improvements:
8110 - don't clobber an external CFLAGS in ./configure
8111 - Make install now works
8112 - create var/lib/tor on make install
8113 - autocreate a tor.sh initscript to help distribs
8114 - autocreate the torrc and sample-server-torrc with correct paths
8116 o Log files and Daemonizing now work:
8117 - If --DebugLogFile is specified, log to it at -l debug
8118 - If --LogFile is specified, use it instead of commandline
8119 - If --RunAsDaemon is set, tor forks and backgrounds on startup