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.2.32 - 2011-08-27
7 The Tor 0.2.2 release series is dedicated to the memory of Andreas
8 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
9 a founder of the PETS community, a leader in our field, a mentor,
10 and a friend. He left us with these words: "I had the possibility
11 to contribute to this world that is not as it should be. I hope I
12 could help in some areas to make the world a better place, and that
13 I could also encourage other people to be engaged in improving the
14 world. Please, stay engaged. This world needs you, your love, your
15 initiative -- now I cannot be part of that anymore."
17 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
18 ready. More than two years in the making, this release features improved
19 client performance and hidden service reliability, better compatibility
20 for Android, correct behavior for bridges that listen on more than
21 one address, more extensible and flexible directory object handling,
22 better reporting of network statistics, improved code security, and
23 many many other features and bugfixes.
25 o Major features (client performance):
26 - When choosing which cells to relay first, relays now favor circuits
27 that have been quiet recently, to provide lower latency for
28 low-volume circuits. By default, relays enable or disable this
29 feature based on a setting in the consensus. They can override
30 this default by using the new "CircuitPriorityHalflife" config
31 option. Design and code by Ian Goldberg, Can Tang, and Chris
33 - Directory authorities now compute consensus weightings that instruct
34 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
35 and no flag. Clients use these weightings to distribute network load
36 more evenly across these different relay types. The weightings are
37 in the consensus so we can change them globally in the future. Extra
38 thanks to "outofwords" for finding some nasty security bugs in
39 the first implementation of this feature.
41 o Major features (client performance, circuit build timeout):
42 - Tor now tracks how long it takes to build client-side circuits
43 over time, and adapts its timeout to local network performance.
44 Since a circuit that takes a long time to build will also provide
45 bad performance, we get significant latency improvements by
46 discarding the slowest 20% of circuits. Specifically, Tor creates
47 circuits more aggressively than usual until it has enough data
48 points for a good timeout estimate. Implements proposal 151.
49 - Circuit build timeout constants can be controlled by consensus
50 parameters. We set good defaults for these parameters based on
51 experimentation on broadband and simulated high-latency links.
52 - Circuit build time learning can be disabled via consensus parameter
53 or by the client via a LearnCircuitBuildTimeout config option. We
54 also automatically disable circuit build time calculation if either
55 AuthoritativeDirectory is set, or if we fail to write our state
56 file. Implements ticket 1296.
58 o Major features (relays use their capacity better):
59 - Set SO_REUSEADDR socket option on all sockets, not just
60 listeners. This should help busy exit nodes avoid running out of
61 useable ports just because all the ports have been used in the
62 near past. Resolves issue 2850.
63 - Relays now save observed peak bandwidth throughput rates to their
64 state file (along with total usage, which was already saved),
65 so that they can determine their correct estimated bandwidth on
66 restart. Resolves bug 1863, where Tor relays would reset their
67 estimated bandwidth to 0 after restarting.
68 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
69 should give us approximately 40-50% more Guard-flagged nodes,
70 improving the anonymity the Tor network can provide and also
71 decreasing the dropoff in throughput that relays experience when
72 they first get the Guard flag.
73 - Directory authorities now take changes in router IP address and
74 ORPort into account when determining router stability. Previously,
75 if a router changed its IP or ORPort, the authorities would not
76 treat it as having any downtime for the purposes of stability
77 calculation, whereas clients would experience downtime since the
78 change would take a while to propagate to them. Resolves issue 1035.
79 - New AccelName and AccelDir options add support for dynamic OpenSSL
80 hardware crypto acceleration engines.
82 o Major features (relays control their load better):
83 - Exit relays now try harder to block exit attempts from unknown
84 relays, to make it harder for people to use them as one-hop proxies
85 a la tortunnel. Controlled by the refuseunknownexits consensus
86 parameter (currently enabled), or you can override it on your
87 relay with the RefuseUnknownExits torrc option. Resolves bug 1751;
88 based on a variant of proposal 163.
89 - Add separate per-conn write limiting to go with the per-conn read
90 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
91 but never per-conn write limits.
92 - New consensus params "bwconnrate" and "bwconnburst" to let us
93 rate-limit client connections as they enter the network. It's
94 controlled in the consensus so we can turn it on and off for
95 experiments. It's starting out off. Based on proposal 163.
97 o Major features (controllers):
98 - Export GeoIP information on bridge usage to controllers even if we
99 have not yet been running for 24 hours. Now Vidalia bridge operators
100 can get more accurate and immediate feedback about their
101 contributions to the network.
102 - Add an __OwningControllerProcess configuration option and a
103 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
104 that when it exits, Tor will shut down. Implements feature 3049.
106 o Major features (directory authorities):
107 - Directory authorities now create, vote on, and serve multiple
108 parallel formats of directory data as part of their voting process.
109 Partially implements Proposal 162: "Publish the consensus in
111 - Directory authorities now agree on and publish small summaries
112 of router information that clients can use in place of regular
113 server descriptors. This transition will allow Tor 0.2.3 clients
114 to use far less bandwidth for downloading information about the
115 network. Begins the implementation of Proposal 158: "Clients
116 download consensus + microdescriptors".
117 - The directory voting system is now extensible to use multiple hash
118 algorithms for signatures and resource selection. Newer formats
119 are signed with SHA256, with a possibility for moving to a better
120 hash algorithm in the future.
121 - Directory authorities can now vote on arbitary integer values as
122 part of the consensus process. This is designed to help set
123 network-wide parameters. Implements proposal 167.
125 o Major features and bugfixes (node selection):
126 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
127 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and Strict*Nodes
128 options. Previously, we had been ambiguous in describing what
129 counted as an "exit" node, and what operations exactly "StrictNodes
130 0" would permit. This created confusion when people saw nodes built
131 through unexpected circuits, and made it hard to tell real bugs from
132 surprises. Now the intended behavior is:
133 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
134 a node that delivers user traffic outside the Tor network.
135 . "Entry", in the context of EntryNodes, means a node used as the
136 first hop of a multihop circuit. It doesn't include direct
137 connections to directory servers.
138 . "ExcludeNodes" applies to all nodes.
139 . "StrictNodes" changes the behavior of ExcludeNodes only. When
140 StrictNodes is set, Tor should avoid all nodes listed in
141 ExcludeNodes, even when it will make user requests fail. When
142 StrictNodes is *not* set, then Tor should follow ExcludeNodes
143 whenever it can, except when it must use an excluded node to
144 perform self-tests, connect to a hidden service, provide a
145 hidden service, fulfill a .exit request, upload directory
146 information, or fetch directory information.
147 Collectively, the changes to implement the behavior fix bug 1090.
148 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
149 change during a config reload, mark and discard all our origin
150 circuits. This fix should address edge cases where we change the
151 config options and but then choose a circuit that we created before
153 - Make EntryNodes config option much more aggressive even when
154 StrictNodes is not set. Before it would prepend your requested
155 entrynodes to your list of guard nodes, but feel free to use others
156 after that. Now it chooses only from your EntryNodes if any of
157 those are available, and only falls back to others if a) they're
158 all down and b) StrictNodes is not set.
159 - Now we refresh your entry guards from EntryNodes at each consensus
160 fetch -- rather than just at startup and then they slowly rot as
162 - Add support for the country code "{??}" in torrc options like
163 ExcludeNodes, to indicate all routers of unknown country. Closes
165 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
166 a node is listed in both, it's treated as excluded.
167 - ExcludeNodes now applies to directory nodes -- as a preference if
168 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
169 Don't exclude all the directory authorities and set StrictNodes to 1
170 unless you really want your Tor to break.
171 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
172 - ExcludeExitNodes now overrides .exit requests.
173 - We don't use bridges listed in ExcludeNodes.
174 - When StrictNodes is 1:
175 . We now apply ExcludeNodes to hidden service introduction points
176 and to rendezvous points selected by hidden service users. This
177 can make your hidden service less reliable: use it with caution!
178 . If we have used ExcludeNodes on ourself, do not try relay
179 reachability self-tests.
180 . If we have excluded all the directory authorities, we will not
181 even try to upload our descriptor if we're a relay.
182 . Do not honor .exit requests to an excluded node.
183 - When the set of permitted nodes changes, we now remove any mappings
184 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
186 - We never cannibalize a circuit that had excluded nodes on it, even
187 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
188 - Improve log messages related to excluded nodes.
190 o Major features (misc):
191 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
192 to help Tor build correctly for Android phones.
193 - The options SocksPort, ControlPort, and so on now all accept a
194 value "auto" that opens a socket on an OS-selected port. A
195 new ControlPortWriteToFile option tells Tor to write its
196 actual control port or ports to a chosen file. If the option
197 ControlPortFileGroupReadable is set, the file is created as
198 group-readable. Now users can run two Tor clients on the same
199 system without needing to manually mess with parameters. Resolves
201 - Tor now supports tunneling all of its outgoing connections over
202 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
203 configuration options. Code by Christopher Davis.
205 o Code security improvements:
206 - Replace all potentially sensitive memory comparison operations
207 with versions whose runtime does not depend on the data being
208 compared. This will help resist a class of attacks where an
209 adversary can use variations in timing information to learn
210 sensitive data. Fix for one case of bug 3122. (Safe memcmp
211 implementation by Robert Ransom based partially on code by DJB.)
212 - Enable Address Space Layout Randomization (ASLR) and Data Execution
213 Prevention (DEP) by default on Windows to make it harder for
214 attackers to exploit vulnerabilities. Patch from John Brooks.
215 - New "--enable-gcc-hardening" ./configure flag (off by default)
216 to turn on gcc compile time hardening options. It ensures
217 that signed ints have defined behavior (-fwrapv), enables
218 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
219 with canaries (-fstack-protector-all), turns on ASLR protection if
220 supported by the kernel (-fPIE, -pie), and adds additional security
221 related warnings. Verified to work on Mac OS X and Debian Lenny.
222 - New "--enable-linker-hardening" ./configure flag (off by default)
223 to turn on ELF specific hardening features (relro, now). This does
224 not work with Mac OS X or any other non-ELF binary format.
225 - Always search the Windows system directory for system DLLs, and
226 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
227 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
228 current and future memory pages via mlockall(). On supported
229 platforms (modern Linux and probably BSD but not Windows or OS X),
230 this should effectively disable any and all attempts to page out
231 memory. This option requires that you start your Tor as root --
232 if you use DisableAllSwap, please consider using the User option
233 to properly reduce the privileges of your Tor.
235 o Major bugfixes (crashes):
236 - Fix crash bug on platforms where gmtime and localtime can return
237 NULL. Windows 7 users were running into this one. Fixes part of bug
238 2077. Bugfix on all versions of Tor. Found by boboper.
239 - Introduce minimum/maximum values that clients will believe
240 from the consensus. Now we'll have a better chance to avoid crashes
241 or worse when a consensus param has a weird value.
242 - Fix a rare crash bug that could occur when a client was configured
243 with a large number of bridges. Fixes bug 2629; bugfix on
244 0.2.1.2-alpha. Bugfix by trac user "shitlei".
245 - Do not crash when our configuration file becomes unreadable, for
246 example due to a permissions change, between when we start up
247 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
249 - If we're in the pathological case where there's no exit bandwidth
250 but there is non-exit bandwidth, or no guard bandwidth but there
251 is non-guard bandwidth, don't crash during path selection. Bugfix
253 - Fix a crash bug when trying to initialize the evdns module in
254 Libevent 2. Bugfix on 0.2.1.16-rc.
256 o Major bugfixes (stability):
257 - Fix an assert in parsing router descriptors containing IPv6
258 addresses. This one took down the directory authorities when
259 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
260 - Fix an uncommon assertion failure when running with DNSPort under
261 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
262 - Treat an unset $HOME like an empty $HOME rather than triggering an
263 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
264 - More gracefully handle corrupt state files, removing asserts
265 in favor of saving a backup and resetting state.
266 - Instead of giving an assertion failure on an internal mismatch
267 on estimated freelist size, just log a BUG warning and try later.
268 Mitigates but does not fix bug 1125.
269 - Fix an assert that got triggered when using the TestingTorNetwork
270 configuration option and then issuing a GETINFO config-text control
271 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
272 - If the cached cert file is unparseable, warn but don't exit.
274 o Privacy fixes (relays/bridges):
275 - Don't list Windows capabilities in relay descriptors. We never made
276 use of them, and maybe it's a bad idea to publish them. Bugfix
278 - If the Nickname configuration option isn't given, Tor would pick a
279 nickname based on the local hostname as the nickname for a relay.
280 Because nicknames are not very important in today's Tor and the
281 "Unnamed" nickname has been implemented, this is now problematic
282 behavior: It leaks information about the hostname without being
283 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
284 introduced the Unnamed nickname. Reported by tagnaq.
285 - Maintain separate TLS contexts and certificates for incoming and
286 outgoing connections in bridge relays. Previously we would use the
287 same TLS contexts and certs for incoming and outgoing connections.
288 Bugfix on 0.2.0.3-alpha; addresses bug 988.
289 - Maintain separate identity keys for incoming and outgoing TLS
290 contexts in bridge relays. Previously we would use the same
291 identity keys for incoming and outgoing TLS contexts. Bugfix on
292 0.2.0.3-alpha; addresses the other half of bug 988.
293 - Make the bridge directory authority refuse to answer directory
294 requests for "all descriptors". It used to include bridge
295 descriptors in its answer, which was a major information leak.
296 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
298 o Privacy fixes (clients):
299 - When receiving a hidden service descriptor, check that it is for
300 the hidden service we wanted. Previously, Tor would store any
301 hidden service descriptors that a directory gave it, whether it
302 wanted them or not. This wouldn't have let an attacker impersonate
303 a hidden service, but it did let directories pre-seed a client
304 with descriptors that it didn't want. Bugfix on 0.0.6.
305 - Start the process of disabling ".exit" address notation, since it
306 can be used for a variety of esoteric application-level attacks
307 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
309 - Reject attempts at the client side to open connections to private
310 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
311 a randomly chosen exit node. Attempts to do so are always
312 ill-defined, generally prevented by exit policies, and usually
313 in error. This will also help to detect loops in transparent
314 proxy configurations. You can disable this feature by setting
315 "ClientRejectInternalAddresses 0" in your torrc.
316 - Log a notice when we get a new control connection. Now it's easier
317 for security-conscious users to recognize when a local application
318 is knocking on their controller door. Suggested by bug 1196.
320 o Privacy fixes (newnym):
321 - Avoid linkability based on cached hidden service descriptors: forget
322 all hidden service descriptors cached as a client when processing a
323 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
324 - On SIGHUP, do not clear out all TrackHostExits mappings, client
325 DNS cache entries, and virtual address mappings: that's what
326 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
327 - Don't attach new streams to old rendezvous circuits after SIGNAL
328 NEWNYM. Previously, we would keep using an existing rendezvous
329 circuit if it remained open (i.e. if it were kept open by a
330 long-lived stream, or if a new stream were attached to it before
331 Tor could notice that it was old and no longer in use). Bugfix on
332 0.1.1.15-rc; fixes bug 3375.
334 o Major bugfixes (relay bandwidth accounting):
335 - Fix a bug that could break accounting on 64-bit systems with large
336 time_t values, making them hibernate for impossibly long intervals.
337 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
338 - Fix a bug in bandwidth accounting that could make us use twice
339 the intended bandwidth when our interval start changes due to
340 daylight saving time. Now we tolerate skew in stored vs computed
341 interval starts: if the start of the period changes by no more than
342 50% of the period's duration, we remember bytes that we transferred
343 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
345 o Major bugfixes (bridges):
346 - Bridges now use "reject *:*" as their default exit policy. Bugfix
347 on 0.2.0.3-alpha. Fixes bug 1113.
348 - If you configure your bridge with a known identity fingerprint,
349 and the bridge authority is unreachable (as it is in at least
350 one country now), fall back to directly requesting the descriptor
351 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
353 - Fix a bug where bridge users who configure the non-canonical
354 address of a bridge automatically switch to its canonical
355 address. If a bridge listens at more than one address, it
356 should be able to advertise those addresses independently and
357 any non-blocked addresses should continue to work. Bugfix on Tor
358 0.2.0.3-alpha. Fixes bug 2510.
359 - If you configure Tor to use bridge A, and then quit and
360 configure Tor to use bridge B instead (or if you change Tor
361 to use bridge B via the controller), it would happily continue
362 to use bridge A if it's still reachable. While this behavior is
363 a feature if your goal is connectivity, in some scenarios it's a
364 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
365 - When the controller configures a new bridge, don't wait 10 to 60
366 seconds before trying to fetch its descriptor. Bugfix on
367 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
369 o Major bugfixes (directory authorities):
370 - Many relays have been falling out of the consensus lately because
371 not enough authorities know about their descriptor for them to get
372 a majority of votes. When we deprecated the v2 directory protocol,
373 we got rid of the only way that v3 authorities can hear from each
374 other about other descriptors. Now authorities examine every v3
375 vote for new descriptors, and fetch them from that authority. Bugfix
377 - Authorities could be tricked into giving out the Exit flag to relays
378 that didn't allow exiting to any ports. This bug could screw
379 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
380 1238. Bug discovered by Martin Kowalczyk.
381 - If all authorities restart at once right before a consensus vote,
382 nobody will vote about "Running", and clients will get a consensus
383 with no usable relays. Instead, authorities refuse to build a
384 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
386 o Major bugfixes (stream-level fairness):
387 - When receiving a circuit-level SENDME for a blocked circuit, try
388 to package cells fairly from all the streams that had previously
389 been blocked on that circuit. Previously, we had started with the
390 oldest stream, and allowed each stream to potentially exhaust
391 the circuit's package window. This gave older streams on any
392 given circuit priority over newer ones. Fixes bug 1937. Detected
393 originally by Camilo Viecco. This bug was introduced before the
394 first Tor release, in svn commit r152: it is the new winner of
395 the longest-lived bug prize.
396 - Fix a stream fairness bug that would cause newer streams on a given
397 circuit to get preference when reading bytes from the origin or
398 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
399 introduced before the first Tor release, in svn revision r152.
400 - When the exit relay got a circuit-level sendme cell, it started
401 reading on the exit streams, even if had 500 cells queued in the
402 circuit queue already, so the circuit queue just grew and grew in
403 some cases. We fix this by not re-enabling reading on receipt of a
404 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
405 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
407 - Newly created streams were allowed to read cells onto circuits,
408 even if the circuit's cell queue was blocked and waiting to drain.
409 This created potential unfairness, as older streams would be
410 blocked, but newer streams would gladly fill the queue completely.
411 We add code to detect this situation and prevent any stream from
412 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
415 o Major bugfixes (hidden services):
416 - Apply circuit timeouts to opened hidden-service-related circuits
417 based on the correct start time. Previously, we would apply the
418 circuit build timeout based on time since the circuit's creation;
419 it was supposed to be applied based on time since the circuit
420 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
421 - Improve hidden service robustness: When we find that we have
422 extended a hidden service's introduction circuit to a relay not
423 listed as an introduction point in the HS descriptor we currently
424 have, retry with an introduction point from the current
425 descriptor. Previously we would just give up. Fixes bugs 1024 and
426 1930; bugfix on 0.2.0.10-alpha.
427 - Directory authorities now use data collected from their own
428 uptime observations when choosing whether to assign the HSDir flag
429 to relays, instead of trusting the uptime value the relay reports in
430 its descriptor. This change helps prevent an attack where a small
431 set of nodes with frequently-changing identity keys can blackhole
432 a hidden service. (Only authorities need upgrade; others will be
433 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
434 - Stop assigning the HSDir flag to relays that disable their
435 DirPort (and thus will refuse to answer directory requests). This
436 fix should dramatically improve the reachability of hidden services:
437 hidden services and hidden service clients pick six HSDir relays
438 to store and retrieve the hidden service descriptor, and currently
439 about half of the HSDir relays will refuse to work. Bugfix on
440 0.2.0.10-alpha; fixes part of bug 1693.
442 o Major bugfixes (misc):
443 - Clients now stop trying to use an exit node associated with a given
444 destination by TrackHostExits if they fail to reach that exit node.
445 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
446 - Fix a regression that caused Tor to rebind its ports if it receives
447 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
448 - Remove an extra pair of quotation marks around the error
449 message in control-port STATUS_GENERAL BUG events. Bugfix on
450 0.1.2.6-alpha; fixes bug 3732.
452 o Minor features (relays):
453 - Ensure that no empty [dirreq-](read|write)-history lines are added
454 to an extrainfo document. Implements ticket 2497.
455 - When bandwidth accounting is enabled, be more generous with how
456 much bandwidth we'll use up before entering "soft hibernation".
457 Previously, we'd refuse new connections and circuits once we'd
458 used up 95% of our allotment. Now, we use up 95% of our allotment,
459 AND make sure that we have no more than 500MB (or 3 hours of
460 expected traffic, whichever is lower) remaining before we enter
462 - Relays now log the reason for publishing a new relay descriptor,
463 so we have a better chance of hunting down instances of bug 1810.
464 Resolves ticket 3252.
465 - Log a little more clearly about the times at which we're no longer
466 accepting new connections (e.g. due to hibernating). Resolves
468 - When AllowSingleHopExits is set, print a warning to explain to the
469 relay operator why most clients are avoiding her relay.
470 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
471 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
472 clients are already deprecated because of security bugs.
474 o Minor features (network statistics):
475 - Directory mirrors that set "DirReqStatistics 1" write statistics
476 about directory requests to disk every 24 hours. As compared to the
477 "--enable-geoip-stats" ./configure flag in 0.2.1.x, there are a few
478 improvements: 1) stats are written to disk exactly every 24 hours;
479 2) estimated shares of v2 and v3 requests are determined as mean
480 values, not at the end of a measurement period; 3) unresolved
481 requests are listed with country code '??'; 4) directories also
482 measure download times.
483 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
484 number of exit streams and transferred bytes per port to disk every
486 - Relays that set "CellStatistics 1" write statistics on how long
487 cells spend in their circuit queues to disk every 24 hours.
488 - Entry nodes that set "EntryStatistics 1" write statistics on the
489 rough number and origins of connecting clients to disk every 24
491 - Relays that write any of the above statistics to disk and set
492 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
493 their extra-info documents. Implements proposal 166.
495 o Minor features (GeoIP and statistics):
496 - Provide a log message stating which geoip file we're parsing
497 instead of just stating that we're parsing the geoip file.
498 Implements ticket 2432.
499 - Make sure every relay writes a state file at least every 12 hours.
500 Previously, a relay could go for weeks without writing its state
501 file, and on a crash could lose its bandwidth history, capacity
502 estimates, client country statistics, and so on. Addresses bug 3012.
503 - Relays report the number of bytes spent on answering directory
504 requests in extra-info descriptors similar to {read,write}-history.
505 Implements enhancement 1790.
506 - Report only the top 10 ports in exit-port stats in order not to
507 exceed the maximum extra-info descriptor length of 50 KB. Implements
509 - If writing the state file to disk fails, wait up to an hour before
510 retrying again, rather than trying again each second. Fixes bug
511 2346; bugfix on Tor 0.1.1.3-alpha.
512 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
513 when we switch from being a public relay to a bridge. Otherwise
514 there will still be clients that see the relay in their consensus,
515 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes
517 - Update to the August 2 2011 Maxmind GeoLite Country database.
519 o Minor features (clients):
520 - When expiring circuits, use microsecond timers rather than
521 one-second timers. This can avoid an unpleasant situation where a
522 circuit is launched near the end of one second and expired right
523 near the beginning of the next, and prevent fluctuations in circuit
525 - If we've configured EntryNodes and our network goes away and/or all
526 our entrynodes get marked down, optimistically retry them all when
527 a new socks application request appears. Fixes bug 1882.
528 - Always perform router selections using weighted relay bandwidth,
529 even if we don't need a high capacity circuit at the time. Non-fast
530 circuits now only differ from fast ones in that they can use relays
531 not marked with the Fast flag. This "feature" could turn out to
532 be a horrible bug; we should investigate more before it goes into
534 - When we run out of directory information such that we can't build
535 circuits, but then get enough that we can build circuits, log when
536 we actually construct a circuit, so the user has a better chance of
537 knowing what's going on. Fixes bug 1362.
538 - Log SSL state transitions at debug level during handshake, and
539 include SSL states in error messages. This may help debug future
540 SSL handshake issues.
542 o Minor features (directory authorities):
543 - When a router changes IP address or port, authorities now launch
544 a new reachability test for it. Implements ticket 1899.
545 - Directory authorities now reject relays running any versions of
546 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
547 known bugs that keep RELAY_EARLY cells from working on rendezvous
548 circuits. Followup to fix for bug 2081.
549 - Directory authorities now reject relays running any version of Tor
550 older than 0.2.0.26-rc. That version is the earliest that fetches
551 current directory information correctly. Fixes bug 2156.
552 - Directory authorities now do an immediate reachability check as soon
553 as they hear about a new relay. This change should slightly reduce
554 the time between setting up a relay and getting listed as running
555 in the consensus. It should also improve the time between setting
556 up a bridge and seeing use by bridge users.
557 - Directory authorities no longer launch a TLS connection to every
558 relay as they startup. Now that we have 2k+ descriptors cached,
559 the resulting network hiccup is becoming a burden. Besides,
560 authorities already avoid voting about Running for the first half
561 hour of their uptime.
562 - Directory authorities now log the source of a rejected POSTed v3
563 networkstatus vote, so we can track failures better.
564 - Backport code from 0.2.3.x that allows directory authorities to
565 clean their microdescriptor caches. Needed to resolve bug 2230.
567 o Minor features (hidden services):
568 - Use computed circuit-build timeouts to decide when to launch
569 parallel introduction circuits for hidden services. (Previously,
570 we would retry after 15 seconds.)
571 - Don't allow v0 hidden service authorities to act as clients.
572 Required by fix for bug 3000.
573 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
575 - Make hidden services work better in private Tor networks by not
576 requiring any uptime to join the hidden service descriptor
577 DHT. Implements ticket 2088.
578 - Log (at info level) when purging pieces of hidden-service-client
579 state because of SIGNAL NEWNYM.
581 o Minor features (controller interface):
582 - New "GETINFO net/listeners/(type)" controller command to return
583 a list of addresses and ports that are bound for listeners for a
584 given connection type. This is useful when the user has configured
585 "SocksPort auto" and the controller needs to know which port got
586 chosen. Resolves another part of ticket 3076.
587 - Have the controller interface give a more useful message than
588 "Internal Error" in response to failed GETINFO requests.
589 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
590 event, to give information on the current rate of circuit timeouts
591 over our stored history.
592 - The 'EXTENDCIRCUIT' control port command can now be used with
593 a circ id of 0 and no path. This feature will cause Tor to build
594 a new 'fast' general purpose circuit using its own path selection
596 - Added a BUILDTIMEOUT_SET controller event to describe changes
597 to the circuit build timeout.
598 - New controller command "getinfo config-text". It returns the
599 contents that Tor would write if you send it a SAVECONF command,
600 so the controller can write the file to disk itself.
602 o Minor features (controller protocol):
603 - Add a new ControlSocketsGroupWritable configuration option: when
604 it is turned on, ControlSockets are group-writeable by the default
605 group of the current user. Patch by Jérémy Bobbio; implements
607 - Tor now refuses to create a ControlSocket in a directory that is
608 world-readable (or group-readable if ControlSocketsGroupWritable
609 is 0). This is necessary because some operating systems do not
610 enforce permissions on an AF_UNIX sockets. Permissions on the
611 directory holding the socket, however, seems to work everywhere.
612 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
613 not. This would lead to a cookie that is still not group readable.
614 Closes bug 1843. Suggested by katmagic.
615 - Future-proof the controller protocol a bit by ignoring keyword
616 arguments we do not recognize.
618 o Minor features (more useful logging):
619 - Revise most log messages that refer to nodes by nickname to
620 instead use the "$key=nickname at address" format. This should be
621 more useful, especially since nicknames are less and less likely
622 to be unique. Resolves ticket 3045.
623 - When an HTTPS proxy reports "403 Forbidden", we now explain
624 what it means rather than calling it an unexpected status code.
625 Closes bug 2503. Patch from Michael Yakubovich.
626 - Rate-limit a warning about failures to download v2 networkstatus
627 documents. Resolves part of bug 1352.
628 - Rate-limit the "your application is giving Tor only an IP address"
629 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
630 - Rate-limit "Failed to hand off onionskin" warnings.
631 - When logging a rate-limited warning, we now mention how many messages
632 got suppressed since the last warning.
633 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
634 2 no signature, 4 required" messages about consensus signatures
635 easier to read, and make sure they get logged at the same severity
636 as the messages explaining which keys are which. Fixes bug 1290.
637 - Don't warn when we have a consensus that we can't verify because
638 of missing certificates, unless those certificates are ones
639 that we have been trying and failing to download. Fixes bug 1145.
641 o Minor features (log domains):
642 - Add documentation for configuring logging at different severities in
643 different log domains. We've had this feature since 0.2.1.1-alpha,
644 but for some reason it never made it into the manpage. Fixes
646 - Make it simpler to specify "All log domains except for A and B".
647 Previously you needed to say "[*,~A,~B]". Now you can just say
649 - Add a "LogMessageDomains 1" option to include the domains of log
650 messages along with the messages. Without this, there's no way
651 to use log domains without reading the source or doing a lot
653 - Add a new "Handshake" log domain for activities that happen
654 during the TLS handshake.
656 o Minor features (build process):
657 - Make compilation with clang possible when using
658 "--enable-gcc-warnings" by removing two warning options that clang
659 hasn't implemented yet and by fixing a few warnings. Resolves
661 - Detect platforms that brokenly use a signed size_t, and refuse to
662 build there. Found and analyzed by doorss and rransom.
663 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
665 - Add support for statically linking zlib by specifying
666 "--enable-static-zlib", to go with our support for statically
667 linking openssl and libevent. Resolves bug 1358.
668 - Instead of adding the svn revision to the Tor version string, report
669 the git commit (when we're building from a git checkout).
670 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
672 - New --digests command-line switch to output the digests of the
673 source files Tor was built with.
674 - Generate our manpage and HTML documentation using Asciidoc. This
675 change should make it easier to maintain the documentation, and
676 produce nicer HTML. The build process fails if asciidoc cannot
677 be found and building with asciidoc isn't disabled (via the
678 "--disable-asciidoc" argument to ./configure. Skipping the manpage
679 speeds up the build considerably.
681 o Minor features (options / torrc):
682 - Warn when the same option is provided more than once in a torrc
683 file, on the command line, or in a single SETCONF statement, and
684 the option is one that only accepts a single line. Closes bug 1384.
685 - Warn when the user configures two HiddenServiceDir lines that point
686 to the same directory. Bugfix on 0.0.6 (the version introducing
687 HiddenServiceDir); fixes bug 3289.
688 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
689 do individual connection-level rate limiting of clients. The torrc
690 config options with the same names trump the consensus params, if
691 both are present. Replaces the old "bwconnrate" and "bwconnburst"
692 consensus params which were broken from 0.2.2.7-alpha through
693 0.2.2.14-alpha. Closes bug 1947.
694 - New config option "WarnUnsafeSocks 0" disables the warning that
695 occurs whenever Tor receives a socks handshake using a version of
696 the socks protocol that can only provide an IP address (rather
697 than a hostname). Setups that do DNS locally over Tor are fine,
698 and we shouldn't spam the logs in that case.
699 - New config option "CircuitStreamTimeout" to override our internal
700 timeout schedule for how many seconds until we detach a stream from
701 a circuit and try a new circuit. If your network is particularly
702 slow, you might want to set this to a number like 60.
703 - New options for SafeLogging to allow scrubbing only log messages
704 generated while acting as a relay. Specify "SafeLogging relay" if
705 you want to ensure that only messages known to originate from
706 client use of the Tor process will be logged unsafely.
707 - Time and memory units in the configuration file can now be set to
708 fractional units. For example, "2.5 GB" is now a valid value for
710 - Support line continuations in the torrc config file. If a line
711 ends with a single backslash character, the newline is ignored, and
712 the configuration value is treated as continuing on the next line.
715 o Minor features (unit tests):
716 - Revise our unit tests to use the "tinytest" framework, so we
717 can run tests in their own processes, have smarter setup/teardown
718 code, and so on. The unit test code has moved to its own
719 subdirectory, and has been split into multiple modules.
720 - Add a unit test for cross-platform directory-listing code.
721 - Add some forgotten return value checks during unit tests. Found
723 - Use GetTempDir to find the proper temporary directory location on
724 Windows when generating temporary files for the unit tests. Patch
727 o Minor features (misc):
728 - The "torify" script now uses torsocks where available.
729 - Make Libevent log messages get delivered to controllers later,
730 and not from inside the Libevent log handler. This prevents unsafe
731 reentrant Libevent calls while still letting the log messages
733 - Certain Tor clients (such as those behind check.torproject.org) may
734 want to fetch the consensus in an extra early manner. To enable this
735 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
736 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
737 as only certain clients who must have this information sooner should
739 - Expand homedirs passed to tor-checkkey. This should silence a
740 coverity complaint about passing a user-supplied string into
741 open() without checking it.
742 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
743 used on bridges, and it makes bridge scanning somewhat easier.
744 - Create the /var/run/tor directory on startup on OpenSUSE if it is
745 not already created. Patch from Andreas Stieger. Fixes bug 2573.
747 o Minor bugfixes (relays):
748 - When a relay decides that its DNS is too broken for it to serve
749 as an exit server, it advertised itself as a non-exit, but
750 continued to act as an exit. This could create accidental
751 partitioning opportunities for users. Instead, if a relay is
752 going to advertise reject *:* as its exit policy, it should
753 really act with exit policy "reject *:*". Fixes bug 2366.
754 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
755 - Publish a router descriptor even if generating an extra-info
756 descriptor fails. Previously we would not publish a router
757 descriptor without an extra-info descriptor; this can cause fast
758 exit relays collecting exit-port statistics to drop from the
759 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
760 - When we're trying to guess whether we know our IP address as
761 a relay, we would log various ways that we failed to guess
762 our address, but never log that we ended up guessing it
763 successfully. Now add a log line to help confused and anxious
764 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
765 - For bandwidth accounting, calculate our expected bandwidth rate
766 based on the time during which we were active and not in
767 soft-hibernation during the last interval. Previously, we were
768 also considering the time spent in soft-hibernation. If this
769 was a long time, we would wind up underestimating our bandwidth
770 by a lot, and skewing our wakeup time towards the start of the
771 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
772 - Demote a confusing TLS warning that relay operators might get when
773 someone tries to talk to their ORPort. It is not the operator's
774 fault, nor can they do anything about it. Fixes bug 1364; bugfix
776 - Change "Application request when we're believed to be offline."
777 notice to "Application request when we haven't used client
778 functionality lately.", to clarify that it's not an error. Bugfix
779 on 0.0.9.3; fixes bug 1222.
781 o Minor bugfixes (bridges):
782 - When a client starts or stops using bridges, never use a circuit
783 that was built before the configuration change. This behavior could
784 put at risk a user who uses bridges to ensure that her traffic
785 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
787 - Do not reset the bridge descriptor download status every time we
788 re-parse our configuration or get a configuration change. Fixes
789 bug 3019; bugfix on 0.2.0.3-alpha.
790 - Users couldn't configure a regular relay to be their bridge. It
791 didn't work because when Tor fetched the bridge descriptor, it found
792 that it already had it, and didn't realize that the purpose of the
793 descriptor had changed. Now we replace routers with a purpose other
794 than bridge with bridge descriptors when fetching them. Bugfix on
795 0.1.1.9-alpha. Fixes bug 1776.
796 - In the special case where you configure a public exit relay as your
797 bridge, Tor would be willing to use that exit relay as the last
798 hop in your circuit as well. Now we fail that circuit instead.
799 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
801 o Minor bugfixes (clients):
802 - We now ask the other side of a stream (the client or the exit)
803 for more data on that stream when the amount of queued data on
804 that stream dips low enough. Previously, we wouldn't ask the
805 other side for more data until either it sent us more data (which
806 it wasn't supposed to do if it had exhausted its window!) or we
807 had completely flushed all our queued data. This flow control fix
808 should improve throughput. Fixes bug 2756; bugfix on the earliest
809 released versions of Tor (svn commit r152).
810 - When a client finds that an origin circuit has run out of 16-bit
811 stream IDs, we now mark it as unusable for new streams. Previously,
812 we would try to close the entire circuit. Bugfix on 0.0.6.
813 - Make it explicit that we don't cannibalize one-hop circuits. This
814 happens in the wild, but doesn't turn out to be a problem because
815 we fortunately don't use those circuits. Many thanks to outofwords
816 for the initial analysis and to swissknife who confirmed that
817 two-hop circuits are actually created.
818 - Resolve an edge case in path weighting that could make us misweight
819 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
820 - Make the DNSPort option work with libevent 2.x. Don't alter the
821 behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
823 o Minor bugfixes (directory authorities):
824 - Make directory authorities more accurate at recording when
825 relays that have failed several reachability tests became
826 unreachable, so we can provide more accuracy at assigning Stable,
827 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
828 - Directory authorities are now more robust to hops back in time
829 when calculating router stability. Previously, if a run of uptime
830 or downtime appeared to be negative, the calculation could give
831 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
833 - Directory authorities will now attempt to download consensuses
834 if their own efforts to make a live consensus have failed. This
835 change means authorities that restart will fetch a valid
836 consensus, and it means authorities that didn't agree with the
837 current consensus will still fetch and serve it if it has enough
838 signatures. Bugfix on 0.2.0.9-alpha; fixes bug 1300.
839 - Never vote for a server as "Running" if we have a descriptor for
840 it claiming to be hibernating, and that descriptor was published
841 more recently than our last contact with the server. Bugfix on
842 0.2.0.3-alpha; fixes bug 911.
843 - Directory authorities no longer change their opinion of, or vote on,
844 whether a router is Running, unless they have themselves been
845 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
848 o Minor bugfixes (hidden services):
849 - Log malformed requests for rendezvous descriptors as protocol
850 warnings, not warnings. Also, use a more informative log message
851 in case someone sees it at log level warning without prior
852 info-level messages. Fixes bug 2748; bugfix on 0.2.0.10-alpha.
853 - Accept hidden service descriptors if we think we might be a hidden
854 service directory, regardless of what our consensus says. This
855 helps robustness, since clients and hidden services can sometimes
856 have a more up-to-date view of the network consensus than we do,
857 and if they think that the directory authorities list us a HSDir,
858 we might actually be one. Related to bug 2732; bugfix on
860 - Correct the warning displayed when a rendezvous descriptor exceeds
861 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
863 - Clients and hidden services now use HSDir-flagged relays for hidden
864 service descriptor downloads and uploads even if the relays have no
865 DirPort set and the client has disabled TunnelDirConns. This will
866 eventually allow us to give the HSDir flag to relays with no
867 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
868 - Only limit the lengths of single HS descriptors, even when multiple
869 HS descriptors are published to an HSDir relay in a single POST
870 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
872 o Minor bugfixes (controllers):
873 - Allow GETINFO fingerprint to return a fingerprint even when
874 we have not yet built a router descriptor. Fixes bug 3577;
875 bugfix on 0.2.0.1-alpha.
876 - Send a SUCCEEDED stream event to the controller when a reverse
877 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
878 discovered by katmagic.
879 - Remove a trailing asterisk from "exit-policy/default" in the
880 output of the control port command "GETINFO info/names". Bugfix
882 - Make the SIGNAL DUMP controller command work on FreeBSD. Fixes bug
883 2917. Bugfix on 0.1.1.1-alpha.
884 - When we restart our relay, we might get a successful connection
885 from the outside before we've started our reachability tests,
886 triggering a warning: "ORPort found reachable, but I have no
887 routerinfo yet. Failing to inform controller of success." This
888 bug was harmless unless Tor is running under a controller
889 like Vidalia, in which case the controller would never get a
890 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
892 - When a controller changes TrackHostExits, remove mappings for
893 hosts that should no longer have their exits tracked. Bugfix on
895 - When a controller changes VirtualAddrNetwork, remove any mappings
896 for hosts that were automapped to the old network. Bugfix on
898 - When a controller changes one of the AutomapHosts* options, remove
899 any mappings for hosts that should no longer be automapped. Bugfix
901 - Fix an off-by-one error in calculating some controller command
902 argument lengths. Fortunately, this mistake is harmless since
903 the controller code does redundant NUL termination too. Found by
904 boboper. Bugfix on 0.1.1.1-alpha.
905 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
906 would return "551 Internal error" rather than "552 Unrecognized key
907 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
908 - Don't spam the controller with events when we have no file
909 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
910 for log messages was already solved from bug 748.)
911 - Emit a GUARD DROPPED controller event for a case we missed.
912 - Ensure DNS requests launched by "RESOLVE" commands from the
913 controller respect the __LeaveStreamsUnattached setconf options. The
914 same goes for requests launched via DNSPort or transparent
915 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
917 o Minor bugfixes (config options):
918 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
919 Change the limit to 512 characters by removing base64 newlines.
920 Fixes bug 2752. Fix by Michael Yakubovich.
921 - Complain if PublishServerDescriptor is given multiple arguments that
922 include 0 or 1. This configuration will be rejected in the future.
923 Bugfix on 0.2.0.1-alpha; closes bug 1107.
924 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
925 Bugfix on 0.2.0.13-alpha; closes bug 928.
927 o Minor bugfixes (log subsystem fixes):
928 - When unable to format an address as a string, report its value
929 as "???" rather than reusing the last formatted address. Bugfix
931 - Be more consistent in our treatment of file system paths. "~" should
932 get expanded to the user's home directory in the Log config option.
933 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
934 feature for the -f and --DataDirectory options.
936 o Minor bugfixes (memory management):
937 - Don't stack-allocate the list of supplementary GIDs when we're
938 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
939 could take up to 256K, which is way too much stack. Found by
940 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
941 - Save a couple bytes in memory allocation every time we escape
942 certain characters in a string. Patch from Florian Zumbiehl.
944 o Minor bugfixes (protocol correctness):
945 - When checking for 1024-bit keys, check for 1024 bits, not 128
946 bytes. This allows Tor to correctly discard keys of length 1017
947 through 1023. Bugfix on 0.0.9pre5.
948 - Require that introduction point keys and onion handshake keys
949 have a public exponent of 65537. Starts to fix bug 3207; bugfix
951 - Handle SOCKS messages longer than 128 bytes long correctly, rather
952 than waiting forever for them to finish. Fixes bug 2330; bugfix
953 on 0.2.0.16-alpha. Found by doorss.
954 - Never relay a cell for a circuit we have already destroyed.
955 Between marking a circuit as closeable and finally closing it,
956 it may have been possible for a few queued cells to get relayed,
957 even though they would have been immediately dropped by the next
958 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
959 - Never queue a cell for a circuit that's already been marked
961 - Fix a spec conformance issue: the network-status-version token
962 must be the first token in a v3 consensus or vote. Discovered by
963 "parakeep". Bugfix on 0.2.0.3-alpha.
964 - A networkstatus vote must contain exactly one signature. Spec
965 conformance issue. Bugfix on 0.2.0.3-alpha.
966 - When asked about a DNS record type we don't support via a
967 client DNSPort, reply with NOTIMPL rather than an empty
968 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
969 - Make more fields in the controller protocol case-insensitive, since
970 control-spec.txt said they were.
972 o Minor bugfixes (log messages):
973 - Fix a log message that said "bits" while displaying a value in
974 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
976 - Downgrade "no current certificates known for authority" message from
977 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
978 - Correctly describe errors that occur when generating a TLS object.
979 Previously we would attribute them to a failure while generating a
980 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
982 - Fix an instance where a Tor directory mirror might accidentally
983 log the IP address of a misbehaving Tor client. Bugfix on
985 - Stop logging at severity 'warn' when some other Tor client tries
986 to establish a circuit with us using weak DH keys. It's a protocol
987 violation, but that doesn't mean ordinary users need to hear about
988 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
989 - If your relay can't keep up with the number of incoming create
990 cells, it would log one warning per failure into your logs. Limit
991 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
993 o Minor bugfixes (build fixes):
994 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
995 - When warning about missing zlib development packages during compile,
996 give the correct package names. Bugfix on 0.2.0.1-alpha.
997 - Fix warnings that newer versions of autoconf produce during
998 ./autogen.sh. These warnings appear to be harmless in our case,
999 but they were extremely verbose. Fixes bug 2020.
1000 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
1003 o Minor bugfixes (portability):
1004 - Write several files in text mode, on OSes that distinguish text
1005 mode from binary mode (namely, Windows). These files are:
1006 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
1007 that collect those statistics; 'client_keys' and 'hostname' for
1008 hidden services that use authentication; and (in the tor-gencert
1009 utility) newly generated identity and signing keys. Previously,
1010 we wouldn't specify text mode or binary mode, leading to an
1011 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
1012 the DirRecordUsageByCountry option which would have triggered
1013 the assertion failure was added), although this assertion failure
1014 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
1015 - Selectively disable deprecation warnings on OS X because Lion
1016 started deprecating the shipped copy of openssl. Fixes bug 3643.
1017 - Use a wide type to hold sockets when built for 64-bit Windows.
1019 - Fix an issue that prevented static linking of libevent on
1020 some platforms (notably Linux). Fixes bug 2698; bugfix on 0.2.1.23,
1021 where we introduced the "--with-static-libevent" configure option.
1022 - Fix a bug with our locking implementation on Windows that couldn't
1023 correctly detect when a file was already locked. Fixes bug 2504,
1024 bugfix on 0.2.1.6-alpha.
1025 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
1027 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
1028 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
1031 o Minor bugfixes (code correctness):
1032 - Always NUL-terminate the sun_path field of a sockaddr_un before
1033 passing it to the kernel. (Not a security issue: kernels are
1034 smart enough to reject bad sockaddr_uns.) Found by Coverity;
1035 CID #428. Bugfix on Tor 0.2.0.3-alpha.
1036 - Make connection_printf_to_buf()'s behaviour sane. Its callers
1037 expect it to emit a CRLF iff the format string ends with CRLF;
1038 it actually emitted a CRLF iff (a) the format string ended with
1039 CRLF or (b) the resulting string was over 1023 characters long or
1040 (c) the format string did not end with CRLF *and* the resulting
1041 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
1042 fixes part of bug 3407.
1043 - Make send_control_event_impl()'s behaviour sane. Its callers
1044 expect it to always emit a CRLF at the end of the string; it
1045 might have emitted extra control characters as well. Bugfix on
1046 0.1.1.9-alpha; fixes another part of bug 3407.
1047 - Make crypto_rand_int() check the value of its input correctly.
1048 Previously, it accepted values up to UINT_MAX, but could return a
1049 negative number if given a value above INT_MAX+1. Found by George
1050 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
1051 - Fix a potential null-pointer dereference while computing a
1052 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
1054 - If we fail to compute the identity digest of a v3 legacy keypair,
1055 warn, and don't use a buffer-full of junk instead. Bugfix on
1056 0.2.1.1-alpha; fixes bug 3106.
1057 - Resolve an untriggerable issue in smartlist_string_num_isin(),
1058 where if the function had ever in the future been used to check
1059 for the presence of a too-large number, it would have given an
1060 incorrect result. (Fortunately, we only used it for 16-bit
1061 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
1062 - Be more careful about reporting the correct error from a failed
1063 connect() system call. Under some circumstances, it was possible to
1064 look at an incorrect value for errno when sending the end reason.
1065 Bugfix on 0.1.0.1-rc.
1066 - Correctly handle an "impossible" overflow cases in connection byte
1067 counting, where we write or read more than 4GB on an edge connection
1068 in a single second. Bugfix on 0.1.2.8-beta.
1069 - Avoid a double mark-for-free warning when failing to attach a
1070 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
1072 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
1073 found by "cypherpunks". This bug was introduced before the first
1074 Tor release, in svn commit r110.
1075 - Fix a bug in bandwidth history state parsing that could have been
1076 triggered if a future version of Tor ever changed the timing
1077 granularity at which bandwidth history is measured. Bugfix on
1079 - Add assertions to check for overflow in arguments to
1080 base32_encode() and base32_decode(); fix a signed-unsigned
1081 comparison there too. These bugs are not actually reachable in Tor,
1082 but it's good to prevent future errors too. Found by doorss.
1083 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
1085 - Set target port in get_interface_address6() correctly. Bugfix
1086 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
1087 - Fix an impossible-to-actually-trigger buffer overflow in relay
1088 descriptor generation. Bugfix on 0.1.0.15.
1089 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
1091 o Minor bugfixes (code improvements):
1092 - After we free an internal connection structure, overwrite it
1093 with a different memory value than we use for overwriting a freed
1094 internal circuit structure. Should help with debugging. Suggested
1096 - If OpenSSL fails to make a duplicate of a private or public key, log
1097 an error message and try to exit cleanly. May help with debugging
1098 if bug 1209 ever remanifests.
1099 - Some options used different conventions for uppercasing of acronyms
1100 when comparing manpage and source. Fix those in favor of the
1101 manpage, as it makes sense to capitalize acronyms.
1102 - Take a first step towards making or.h smaller by splitting out
1103 function definitions for all source files in src/or/. Leave
1104 structures and defines in or.h for now.
1105 - Remove a few dead assignments during router parsing. Found by
1107 - Don't use 1-bit wide signed bit fields. Found by coverity.
1108 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
1109 None of the cases where we did this before were wrong, but by making
1110 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
1111 - The memarea code now uses a sentinel value at the end of each area
1112 to make sure nothing writes beyond the end of an area. This might
1113 help debug some conceivable causes of bug 930.
1114 - Always treat failure to allocate an RSA key as an unrecoverable
1116 - Add some more defensive programming for architectures that can't
1117 handle unaligned integer accesses. We don't know of any actual bugs
1118 right now, but that's the best time to fix them. Fixes bug 1943.
1120 o Minor bugfixes (misc):
1121 - Fix a rare bug in rend_fn unit tests: we would fail a test when
1122 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
1123 on 0.2.0.10-alpha; fixes bug 1808.
1124 - Where available, use Libevent 2.0's periodic timers so that our
1125 once-per-second cleanup code gets called even more closely to
1126 once per second than it would otherwise. Fixes bug 943.
1127 - Ignore OutboundBindAddress when connecting to localhost.
1128 Connections to localhost need to come _from_ localhost, or else
1129 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
1131 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
1133 - If any of the v3 certs we download are unparseable, we should
1134 actually notice the failure so we don't retry indefinitely. Bugfix
1135 on 0.2.0.x; reported by "rotator".
1136 - When Tor fails to parse a descriptor of any kind, dump it to disk.
1137 Might help diagnosing bug 1051.
1138 - Make our 'torify' script more portable; if we have only one of
1139 'torsocks' or 'tsocks' installed, don't complain to the user;
1140 and explain our warning about tsocks better.
1141 - Fix some urls in the exit notice file and make it XHTML1.1 strict
1142 compliant. Based on a patch from Christian Kujau.
1144 o Documentation changes:
1145 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
1146 - Resolve all doxygen warnings except those for missing documentation.
1148 - Add doxygen documentation for more functions, fields, and types.
1149 - Convert the HACKING file to asciidoc, and add a few new sections
1150 to it, explaining how we use Git, how we make changelogs, and
1151 what should go in a patch.
1152 - Document the default socks host and port (127.0.0.1:9050) for
1154 - Removed some unnecessary files from the source distribution. The
1155 AUTHORS file has now been merged into the people page on the
1156 website. The roadmaps and design doc can now be found in the
1157 projects directory in svn.
1159 o Deprecated and removed features (config):
1160 - Remove the torrc.complete file. It hasn't been kept up to date
1161 and users will have better luck checking out the manpage.
1162 - Remove the HSAuthorityRecordStats option that version 0 hidden
1163 service authorities could use to track statistics of overall v0
1164 hidden service usage.
1165 - Remove the obsolete "NoPublish" option; it has been flagged
1166 as obsolete and has produced a warning since 0.1.1.18-rc.
1167 - Caches no longer download and serve v2 networkstatus documents
1168 unless FetchV2Networkstatus flag is set: these documents haven't
1169 haven't been used by clients or relays since 0.2.0.x. Resolves
1172 o Deprecated and removed features (controller):
1173 - The controller no longer accepts the old obsolete "addr-mappings/"
1174 or "unregistered-servers-" GETINFO values.
1175 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
1176 always on; using them is necessary for correct forward-compatible
1179 o Deprecated and removed features (misc):
1180 - Hidden services no longer publish version 0 descriptors, and clients
1181 do not request or use version 0 descriptors. However, the old hidden
1182 service authorities still accept and serve version 0 descriptors
1183 when contacted by older hidden services/clients.
1184 - Remove undocumented option "-F" from tor-resolve: it hasn't done
1185 anything since 0.2.1.16-rc.
1186 - Remove everything related to building the expert bundle for OS X.
1187 It has confused many users, doesn't work right on OS X 10.6,
1188 and is hard to get rid of once installed. Resolves bug 1274.
1189 - Remove support for .noconnect style addresses. Nobody was using
1190 them, and they provided another avenue for detecting Tor users
1191 via application-level web tricks.
1192 - When we fixed bug 1038 we had to put in a restriction not to send
1193 RELAY_EARLY cells on rend circuits. This was necessary as long
1194 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
1195 active. Now remove this obsolete check. Resolves bug 2081.
1196 - Remove workaround code to handle directory responses from servers
1197 that had bug 539 (they would send HTTP status 503 responses _and_
1198 send a body too). Since only server versions before
1199 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
1200 keep the workaround in place.
1201 - Remove the old 'fuzzy time' logic. It was supposed to be used for
1202 handling calculations where we have a known amount of clock skew and
1203 an allowed amount of unknown skew. But we only used it in three
1204 places, and we never adjusted the known/unknown skew values. This is
1205 still something we might want to do someday, but if we do, we'll
1206 want to do it differently.
1207 - Remove the "--enable-iphone" option to ./configure. According to
1208 reports from Marco Bonetti, Tor builds fine without any special
1209 tweaking on recent iPhone SDK versions.
1212 Changes in version 0.2.1.30 - 2011-02-23
1213 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
1214 change is a slight tweak to Tor's TLS handshake that makes relays
1215 and bridges that run this new version reachable from Iran again.
1216 We don't expect this tweak will win the arms race long-term, but it
1217 buys us time until we roll out a better solution.
1220 - Stop sending a CLOCK_SKEW controller status event whenever
1221 we fetch directory information from a relay that has a wrong clock.
1222 Instead, only inform the controller when it's a trusted authority
1223 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
1224 the rest of bug 1074.
1225 - Fix a bounds-checking error that could allow an attacker to
1226 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
1228 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
1229 Tor would ignore their RelayBandwidthBurst setting,
1230 potentially using more bandwidth than expected. Bugfix on
1231 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
1232 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
1233 hidserv" in her torrc. The 'hidserv' argument never controlled
1234 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
1237 - Adjust our TLS Diffie-Hellman parameters to match those used by
1239 - Update to the February 1 2011 Maxmind GeoLite Country database.
1242 - Check for and reject overly long directory certificates and
1243 directory tokens before they have a chance to hit any assertions.
1244 Bugfix on 0.2.1.28. Found by "doorss".
1245 - Bring the logic that gathers routerinfos and assesses the
1246 acceptability of circuits into line. This prevents a Tor OP from
1247 getting locked in a cycle of choosing its local OR as an exit for a
1248 path (due to a .exit request) and then rejecting the circuit because
1249 its OR is not listed yet. It also prevents Tor clients from using an
1250 OR running in the same instance as an exit (due to a .exit request)
1251 if the OR does not meet the same requirements expected of an OR
1252 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
1254 o Packaging changes:
1255 - Stop shipping the Tor specs files and development proposal documents
1256 in the tarball. They are now in a separate git repository at
1257 git://git.torproject.org/torspec.git
1258 - Do not include Git version tags as though they are SVN tags when
1259 generating a tarball from inside a repository that has switched
1260 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
1263 Changes in version 0.2.1.29 - 2011-01-15
1264 Tor 0.2.1.29 continues our recent code security audit work. The main
1265 fix resolves a remote heap overflow vulnerability that can allow remote
1266 code execution. Other fixes address a variety of assert and crash bugs,
1267 most of which we think are hard to exploit remotely.
1269 o Major bugfixes (security):
1270 - Fix a heap overflow bug where an adversary could cause heap
1271 corruption. This bug probably allows remote code execution
1272 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
1274 - Prevent a denial-of-service attack by disallowing any
1275 zlib-compressed data whose compression factor is implausibly
1276 high. Fixes part of bug 2324; reported by "doorss".
1277 - Zero out a few more keys in memory before freeing them. Fixes
1278 bug 2384 and part of bug 2385. These key instances found by
1279 "cypherpunks", based on Andrew Case's report about being able
1280 to find sensitive data in Tor's memory space if you have enough
1281 permissions. Bugfix on 0.0.2pre9.
1283 o Major bugfixes (crashes):
1284 - Prevent calls to Libevent from inside Libevent log handlers.
1285 This had potential to cause a nasty set of crashes, especially
1286 if running Libevent with debug logging enabled, and running
1287 Tor with a controller watching for low-severity log messages.
1288 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
1289 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
1290 underflow errors there too. Fixes the other part of bug 2324.
1291 - Fix a bug where we would assert if we ever had a
1292 cached-descriptors.new file (or another file read directly into
1293 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
1294 on 0.2.1.25. Found by doorss.
1295 - Fix some potential asserts and parsing issues with grossly
1296 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
1299 o Minor bugfixes (other):
1300 - Fix a bug with handling misformed replies to reverse DNS lookup
1301 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
1302 bug reported by doorss.
1303 - Fix compilation on mingw when a pthreads compatibility library
1304 has been installed. (We don't want to use it, so we shouldn't
1305 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
1306 - Fix a bug where we would declare that we had run out of virtual
1307 addresses when the address space was only half-exhausted. Bugfix
1309 - Correctly handle the case where AutomapHostsOnResolve is set but
1310 no virtual addresses are available. Fixes bug 2328; bugfix on
1311 0.1.2.1-alpha. Bug found by doorss.
1312 - Correctly handle wrapping around when we run out of virtual
1313 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
1316 - Update to the January 1 2011 Maxmind GeoLite Country database.
1317 - Introduce output size checks on all of our decryption functions.
1320 - Tor does not build packages correctly with Automake 1.6 and earlier;
1321 added a check to Makefile.am to make sure that we're building with
1322 Automake 1.7 or later.
1323 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
1324 because we built it with a too-old version of automake. Thus that
1325 release broke ./configure --enable-openbsd-malloc, which is popular
1326 among really fast exit relays on Linux.
1329 Changes in version 0.2.1.28 - 2010-12-17
1330 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
1331 exploitable bugs. We also took this opportunity to change the IP address
1332 for one of our directory authorities, and to update the geoip database
1336 - Fix a remotely exploitable bug that could be used to crash instances
1337 of Tor remotely by overflowing on the heap. Remote-code execution
1338 hasn't been confirmed, but can't be ruled out. Everyone should
1339 upgrade. Bugfix on the 0.1.1 series and later.
1341 o Directory authority changes:
1342 - Change IP address and ports for gabelmoo (v3 directory authority).
1345 - Update to the December 1 2010 Maxmind GeoLite Country database.
1348 Changes in version 0.2.1.27 - 2010-11-23
1349 Yet another OpenSSL security patch broke its compatibility with Tor:
1350 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
1351 also took this opportunity to fix several crash bugs, integrate a new
1352 directory authority, and update the bundled GeoIP database.
1355 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
1356 No longer set the tlsext_host_name extension on server SSL objects;
1357 but continue to set it on client SSL objects. Our goal in setting
1358 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
1359 bugfix on 0.2.1.1-alpha.
1360 - Do not log messages to the controller while shrinking buffer
1361 freelists. Doing so would sometimes make the controller connection
1362 try to allocate a buffer chunk, which would mess up the internals
1363 of the freelist and cause an assertion failure. Fixes bug 1125;
1364 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
1365 - Learn our external IP address when we're a relay or bridge, even if
1366 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
1367 where we introduced bridge relays that don't need to publish to
1368 be useful. Fixes bug 2050.
1369 - Do even more to reject (and not just ignore) annotations on
1370 router descriptors received anywhere but from the cache. Previously
1371 we would ignore such annotations at first, but cache them to disk
1372 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
1373 - When you're using bridges and your network goes away and your
1374 bridges get marked as down, recover when you attempt a new socks
1375 connection (if the network is back), rather than waiting up to an
1376 hour to try fetching new descriptors for your bridges. Bugfix on
1377 0.2.0.3-alpha; fixes bug 1981.
1380 - Move to the November 2010 Maxmind GeoLite country db (rather
1381 than the June 2009 ip-to-country GeoIP db) for our statistics that
1382 count how many users relays are seeing from each country. Now we'll
1383 have more accurate data, especially for many African countries.
1385 o New directory authorities:
1386 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
1390 - Fix an assertion failure that could occur in directory caches or
1391 bridge users when using a very short voting interval on a testing
1392 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
1394 - Enforce multiplicity rules when parsing annotations. Bugfix on
1395 0.2.0.8-alpha. Found by piebeer.
1396 - Allow handshaking OR connections to take a full KeepalivePeriod
1397 seconds to handshake. Previously, we would close them after
1398 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
1399 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
1401 - When building with --enable-gcc-warnings on OpenBSD, disable
1402 warnings in system headers. This makes --enable-gcc-warnings
1403 pass on OpenBSD 4.8.
1406 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
1407 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
1408 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
1409 Servers can start sending this code when enough clients recognize
1410 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
1411 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
1412 Patch from mingw-san.
1415 - Remove the old debian/ directory from the main Tor distribution.
1416 The official Tor-for-debian git repository lives at the URL
1417 https://git.torproject.org/debian/tor.git
1418 - Stop shipping the old doc/website/ directory in the tarball. We
1419 changed the website format in late 2010, and what we shipped in
1420 0.2.1.26 really wasn't that useful anyway.
1423 Changes in version 0.2.1.26 - 2010-05-02
1424 Tor 0.2.1.26 addresses the recent connection and memory overload
1425 problems we've been seeing on relays, especially relays with their
1426 DirPort open. If your relay has been crashing, or you turned it off
1427 because it used too many resources, give this release a try.
1429 This release also fixes yet another instance of broken OpenSSL libraries
1430 that was causing some relays to drop out of the consensus.
1433 - Teach relays to defend themselves from connection overload. Relays
1434 now close idle circuits early if it looks like they were intended
1435 for directory fetches. Relays are also more aggressive about closing
1436 TLS connections that have no circuits on them. Such circuits are
1437 unlikely to be re-used, and tens of thousands of them were piling
1438 up at the fast relays, causing the relays to run out of sockets
1439 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
1440 their directory fetches over TLS).
1441 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
1442 that claim to be earlier than 0.9.8m, but which have in reality
1443 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
1444 behavior. Possible fix for some cases of bug 1346.
1445 - Directory mirrors were fetching relay descriptors only from v2
1446 directory authorities, rather than v3 authorities like they should.
1447 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
1448 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
1451 - Finally get rid of the deprecated and now harmful notion of "clique
1452 mode", where directory authorities maintain TLS connections to
1456 - In the util/threads test, no longer free the test_mutex before all
1457 worker threads have finished. Bugfix on 0.2.1.6-alpha.
1458 - The master thread could starve the worker threads quite badly on
1459 certain systems, causing them to run only partially in the allowed
1460 window. This resulted in test failures. Now the master thread sleeps
1461 occasionally for a few microseconds while the two worker-threads
1462 compete for the mutex. Bugfix on 0.2.0.1-alpha.
1465 Changes in version 0.2.1.25 - 2010-03-16
1466 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
1467 prevent relays from guessing their IP address correctly. It also fixes
1468 several minor potential security bugs.
1471 - Fix a regression from our patch for bug 1244 that caused relays
1472 to guess their IP address incorrectly if they didn't set Address
1473 in their torrc and/or their address fails to resolve. Bugfix on
1474 0.2.1.23; fixes bug 1269.
1475 - When freeing a session key, zero it out completely. We only zeroed
1476 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
1477 patched by ekir. Fixes bug 1254.
1480 - Fix a dereference-then-NULL-check sequence when publishing
1481 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
1483 - Fix another dereference-then-NULL-check sequence. Bugfix on
1484 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
1485 - Make sure we treat potentially not NUL-terminated strings correctly.
1486 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
1489 Changes in version 0.2.1.24 - 2010-02-21
1490 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
1494 - Work correctly out-of-the-box with even more vendor-patched versions
1495 of OpenSSL. In particular, make it so Debian and OS X don't need
1496 customized patches to run/build.
1499 Changes in version 0.2.1.23 - 2010-02-13
1500 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
1501 again on the latest OS X, and updates the location of a directory
1504 o Major bugfixes (performance):
1505 - We were selecting our guards uniformly at random, and then weighting
1506 which of our guards we'd use uniformly at random. This imbalance
1507 meant that Tor clients were severely limited on throughput (and
1508 probably latency too) by the first hop in their circuit. Now we
1509 select guards weighted by currently advertised bandwidth. We also
1510 automatically discard guards picked using the old algorithm. Fixes
1511 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
1514 - Make Tor work again on the latest OS X: when deciding whether to
1515 use strange flags to turn TLS renegotiation on, detect the OpenSSL
1516 version at run-time, not compile time. We need to do this because
1517 Apple doesn't update its dev-tools headers when it updates its
1518 libraries in a security patch.
1519 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
1520 that could happen on 32-bit platforms with 64-bit time_t. Also fix
1521 a memory leak when requesting a hidden service descriptor we've
1522 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
1526 - Refactor resolve_my_address() to not use gethostbyname() anymore.
1527 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
1530 - Avoid a mad rush at the beginning of each month when each client
1531 rotates half of its guards. Instead we spread the rotation out
1532 throughout the month, but we still avoid leaving a precise timestamp
1533 in the state file about when we first picked the guard. Improves
1534 over the behavior introduced in 0.1.2.17.
1537 Changes in version 0.2.1.22 - 2010-01-19
1538 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
1539 authorities -- it would tell you its whole history of bridge descriptors
1540 if you make the right directory request. This stable update also
1541 rotates two of the seven v3 directory authority keys and locations.
1543 o Directory authority changes:
1544 - Rotate keys (both v3 identity and relay identity) for moria1
1548 - Stop bridge directory authorities from answering dbg-stability.txt
1549 directory queries, which would let people fetch a list of all
1550 bridge identities they track. Bugfix on 0.2.1.6-alpha.
1553 Changes in version 0.2.1.21 - 2009-12-21
1554 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
1555 library. If you use Tor on Linux / Unix and you're getting SSL
1556 renegotiation errors, upgrading should help. We also recommend an
1557 upgrade if you're an exit relay.
1560 - Work around a security feature in OpenSSL 0.9.8l that prevents our
1561 handshake from working unless we explicitly tell OpenSSL that we
1562 are using SSL renegotiation safely. We are, of course, but OpenSSL
1563 0.9.8l won't work unless we say we are.
1564 - Avoid crashing if the client is trying to upload many bytes and the
1565 circuit gets torn down at the same time, or if the flip side
1566 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
1569 - Do not refuse to learn about authority certs and v2 networkstatus
1570 documents that are older than the latest consensus. This bug might
1571 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
1572 Spotted and fixed by xmux.
1573 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
1574 trigger platform-specific option misparsing case found by Coverity
1576 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
1577 trigger assert. Fixes bug 1173.
1580 Changes in version 0.2.1.20 - 2009-10-15
1581 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
1582 services at once, prepares for more performance improvements, and
1583 fixes a bunch of smaller bugs.
1585 The Windows and OS X bundles also include a more recent Vidalia,
1586 and switch from Privoxy to Polipo.
1588 The OS X installers are now drag and drop. It's best to un-install
1589 Tor/Vidalia and then install this new bundle, rather than upgrade. If
1590 you want to upgrade, you'll need to update the paths for Tor and Polipo
1591 in the Vidalia Settings window.
1594 - Send circuit or stream sendme cells when our window has decreased
1595 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
1596 by Karsten when testing the "reduce circuit window" performance
1597 patch. Bugfix on the 54th commit on Tor -- from July 2002,
1598 before the release of Tor 0.0.0. This is the new winner of the
1600 - Fix a remotely triggerable memory leak when a consensus document
1601 contains more than one signature from the same voter. Bugfix on
1603 - Avoid segfault in rare cases when finishing an introduction circuit
1604 as a client and finding out that we don't have an introduction key
1605 for it. Fixes bug 1073. Reported by Aaron Swartz.
1608 - Tor now reads the "circwindow" parameter out of the consensus,
1609 and uses that value for its circuit package window rather than the
1610 default of 1000 cells. Begins the implementation of proposal 168.
1612 o New directory authorities:
1613 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
1615 - Move moria1 and tonga to alternate IP addresses.
1618 - Fix a signed/unsigned compile warning in 0.2.1.19.
1619 - Fix possible segmentation fault on directory authorities. Bugfix on
1621 - Fix an extremely rare infinite recursion bug that could occur if
1622 we tried to log a message after shutting down the log subsystem.
1623 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
1624 - Fix an obscure bug where hidden services on 64-bit big-endian
1625 systems might mis-read the timestamp in v3 introduce cells, and
1626 refuse to connect back to the client. Discovered by "rotor".
1627 Bugfix on 0.2.1.6-alpha.
1628 - We were triggering a CLOCK_SKEW controller status event whenever
1629 we connect via the v2 connection protocol to any relay that has
1630 a wrong clock. Instead, we should only inform the controller when
1631 it's a trusted authority that claims our clock is wrong. Bugfix
1632 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
1633 - We were telling the controller about CHECKING_REACHABILITY and
1634 REACHABILITY_FAILED status events whenever we launch a testing
1635 circuit or notice that one has failed. Instead, only tell the
1636 controller when we want to inform the user of overall success or
1637 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
1639 - Don't warn when we're using a circuit that ends with a node
1640 excluded in ExcludeExitNodes, but the circuit is not used to access
1641 the outside world. This should help fix bug 1090. Bugfix on
1643 - Work around a small memory leak in some versions of OpenSSL that
1644 stopped the memory used by the hostname TLS extension from being
1648 - Add a "getinfo status/accepted-server-descriptor" controller
1649 command, which is the recommended way for controllers to learn
1650 whether our server descriptor has been successfully received by at
1651 least on directory authority. Un-recommend good-server-descriptor
1652 getinfo and status events until we have a better design for them.
1655 Changes in version 0.2.1.19 - 2009-07-28
1656 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
1660 - Make accessing hidden services on 0.2.1.x work right again.
1661 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
1662 part of patch provided by "optimist".
1665 - When a relay/bridge is writing out its identity key fingerprint to
1666 the "fingerprint" file and to its logs, write it without spaces. Now
1667 it will look like the fingerprints in our bridges documentation,
1668 and confuse fewer users.
1671 - Relays no longer publish a new server descriptor if they change
1672 their MaxAdvertisedBandwidth config option but it doesn't end up
1673 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
1674 fixes bug 1026. Patch from Sebastian.
1675 - Avoid leaking memory every time we get a create cell but we have
1676 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
1677 fixes bug 1034. Reported by BarkerJr.
1680 Changes in version 0.2.1.18 - 2009-07-24
1681 Tor 0.2.1.18 lays the foundations for performance improvements,
1682 adds status events to help users diagnose bootstrap problems, adds
1683 optional authentication/authorization for hidden services, fixes a
1684 variety of potential anonymity problems, and includes a huge pile of
1685 other features and bug fixes.
1687 o Major features (clients):
1688 - Start sending "bootstrap phase" status events to the controller,
1689 so it can keep the user informed of progress fetching directory
1690 information and establishing circuits. Also inform the controller
1691 if we think we're stuck at a particular bootstrap phase. Implements
1693 - Clients replace entry guards that were chosen more than a few months
1694 ago. This change should significantly improve client performance,
1695 especially once more people upgrade, since relays that have been
1696 a guard for a long time are currently overloaded.
1697 - Network status consensus documents and votes now contain bandwidth
1698 information for each relay. Clients use the bandwidth values
1699 in the consensus, rather than the bandwidth values in each
1700 relay descriptor. This approach opens the door to more accurate
1701 bandwidth estimates once the directory authorities start doing
1702 active measurements. Implements part of proposal 141.
1704 o Major features (relays):
1705 - Disable and refactor some debugging checks that forced a linear scan
1706 over the whole server-side DNS cache. These accounted for over 50%
1707 of CPU time on a relatively busy exit node's gprof profile. Also,
1708 disable some debugging checks that appeared in exit node profile
1709 data. Found by Jacob.
1710 - New DirPortFrontPage option that takes an html file and publishes
1711 it as "/" on the DirPort. Now relay operators can provide a
1712 disclaimer without needing to set up a separate webserver. There's
1713 a sample disclaimer in contrib/tor-exit-notice.html.
1715 o Major features (hidden services):
1716 - Make it possible to build hidden services that only certain clients
1717 are allowed to connect to. This is enforced at several points,
1718 so that unauthorized clients are unable to send INTRODUCE cells
1719 to the service, or even (depending on the type of authentication)
1720 to learn introduction points. This feature raises the bar for
1721 certain kinds of active attacks against hidden services. Design
1722 and code by Karsten Loesing. Implements proposal 121.
1723 - Relays now store and serve v2 hidden service descriptors by default,
1724 i.e., the new default value for HidServDirectoryV2 is 1. This is
1725 the last step in proposal 114, which aims to make hidden service
1726 lookups more reliable.
1728 o Major features (path selection):
1729 - ExitNodes and Exclude*Nodes config options now allow you to restrict
1730 by country code ("{US}") or IP address or address pattern
1731 ("255.128.0.0/16"). Patch from Robert Hogan. It still needs some
1732 refinement to decide what config options should take priority if
1733 you ask to both use a particular node and exclude it.
1735 o Major features (misc):
1736 - When building a consensus, do not include routers that are down.
1737 This cuts down 30% to 40% on consensus size. Implements proposal
1739 - New TestingTorNetwork config option to allow adjustment of
1740 previously constant values that could slow bootstrapping. Implements
1741 proposal 135. Patch from Karsten.
1742 - Convert many internal address representations to optionally hold
1743 IPv6 addresses. Generate and accept IPv6 addresses in many protocol
1744 elements. Make resolver code handle nameservers located at IPv6
1746 - More work on making our TLS handshake blend in: modify the list
1747 of ciphers advertised by OpenSSL in client mode to even more
1748 closely resemble a common web browser. We cheat a little so that
1749 we can advertise ciphers that the locally installed OpenSSL doesn't
1751 - Use the TLS1 hostname extension to more closely resemble browser
1754 o Security fixes (anonymity/entropy):
1755 - Never use a connection with a mismatched address to extend a
1756 circuit, unless that connection is canonical. A canonical
1757 connection is one whose address is authenticated by the router's
1758 identity key, either in a NETINFO cell or in a router descriptor.
1759 - Implement most of proposal 110: The first K cells to be sent
1760 along a circuit are marked as special "early" cells; only K "early"
1761 cells will be allowed. Once this code is universal, we can block
1762 certain kinds of denial-of-service attack by requiring that EXTEND
1763 commands must be sent using an "early" cell.
1764 - Resume using OpenSSL's RAND_poll() for better (and more portable)
1765 cross-platform entropy collection again. We used to use it, then
1766 stopped using it because of a bug that could crash systems that
1767 called RAND_poll when they had a lot of fds open. It looks like the
1768 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
1769 at startup, and to call RAND_poll() when we reseed later only if
1770 we have a non-buggy OpenSSL version.
1771 - When the client is choosing entry guards, now it selects at most
1772 one guard from a given relay family. Otherwise we could end up with
1773 all of our entry points into the network run by the same operator.
1774 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
1775 - Do not use or believe expired v3 authority certificates. Patch
1776 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
1777 - Drop begin cells to a hidden service if they come from the middle
1778 of a circuit. Patch from lark.
1779 - When we erroneously receive two EXTEND cells for the same circuit
1780 ID on the same connection, drop the second. Patch from lark.
1781 - Authorities now vote for the Stable flag for any router whose
1782 weighted MTBF is at least 5 days, regardless of the mean MTBF.
1783 - Clients now never report any stream end reason except 'MISC'.
1784 Implements proposal 148.
1786 o Major bugfixes (crashes):
1787 - Parse dates and IPv4 addresses in a locale- and libc-independent
1788 manner, to avoid platform-dependent behavior on malformed input.
1789 - Fix a crash that occurs on exit nodes when a nameserver request
1790 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
1791 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
1793 - Do not assume that a stack-allocated character array will be
1794 64-bit aligned on platforms that demand that uint64_t access is
1795 aligned. Possible fix for bug 604.
1796 - Resolve a very rare crash bug that could occur when the user forced
1797 a nameserver reconfiguration during the middle of a nameserver
1798 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
1799 - Avoid a "0 divided by 0" calculation when calculating router uptime
1800 at directory authorities. Bugfix on 0.2.0.8-alpha.
1801 - Fix an assertion bug in parsing policy-related options; possible fix
1803 - Rate-limit too-many-sockets messages: when they happen, they happen
1804 a lot and end up filling up the disk. Resolves bug 748.
1805 - Fix a race condition that could cause crashes or memory corruption
1806 when running as a server with a controller listening for log
1808 - Avoid crashing when we have a policy specified in a DirPolicy or
1809 SocksPolicy or ReachableAddresses option with ports set on it,
1810 and we re-load the policy. May fix bug 996.
1811 - Fix an assertion failure on 64-bit platforms when we allocated
1812 memory right up to the end of a memarea, then realigned the memory
1813 one step beyond the end. Fixes a possible cause of bug 930.
1814 - Protect the count of open sockets with a mutex, so we can't
1815 corrupt it when two threads are closing or opening sockets at once.
1816 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
1818 o Major bugfixes (clients):
1819 - Discard router descriptors as we load them if they are more than
1820 five days old. Otherwise if Tor is off for a long time and then
1821 starts with cached descriptors, it will try to use the onion keys
1822 in those obsolete descriptors when building circuits. Fixes bug 887.
1823 - When we choose to abandon a new entry guard because we think our
1824 older ones might be better, close any circuits pending on that
1825 new entry guard connection. This fix should make us recover much
1826 faster when our network is down and then comes back. Bugfix on
1827 0.1.2.8-beta; found by lodger.
1828 - When Tor clients restart after 1-5 days, they discard all their
1829 cached descriptors as too old, but they still use the cached
1830 consensus document. This approach is good for robustness, but
1831 bad for performance: since they don't know any bandwidths, they
1832 end up choosing at random rather than weighting their choice by
1833 speed. Fixed by the above feature of putting bandwidths in the
1836 o Major bugfixes (relays):
1837 - Relays were falling out of the networkstatus consensus for
1838 part of a day if they changed their local config but the
1839 authorities discarded their new descriptor as "not sufficiently
1840 different". Now directory authorities accept a descriptor as changed
1841 if BandwidthRate or BandwidthBurst changed. Partial fix for bug 962;
1843 - Ensure that two circuits can never exist on the same connection
1844 with the same circuit ID, even if one is marked for close. This
1845 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
1846 - Directory authorities were neglecting to mark relays down in their
1847 internal histories if the relays fall off the routerlist without
1848 ever being found unreachable. So there were relays in the histories
1849 that haven't been seen for eight months, and are listed as being
1850 up for eight months. This wreaked havoc on the "median wfu" and
1851 "median mtbf" calculations, in turn making Guard and Stable flags
1852 wrong, hurting network performance. Fixes bugs 696 and 969. Bugfix
1855 o Major bugfixes (hidden services):
1856 - When establishing a hidden service, introduction points that
1857 originate from cannibalized circuits were completely ignored
1858 and not included in rendezvous service descriptors. This might
1859 have been another reason for delay in making a hidden service
1860 available. Bugfix from long ago (0.0.9.x?)
1862 o Major bugfixes (memory and resource management):
1863 - Fixed some memory leaks -- some quite frequent, some almost
1864 impossible to trigger -- based on results from Coverity.
1865 - Speed up parsing and cut down on memory fragmentation by using
1866 stack-style allocations for parsing directory objects. Previously,
1867 this accounted for over 40% of allocations from within Tor's code
1868 on a typical directory cache.
1869 - Use a Bloom filter rather than a digest-based set to track which
1870 descriptors we need to keep around when we're cleaning out old
1871 router descriptors. This speeds up the computation significantly,
1872 and may reduce fragmentation.
1874 o New/changed config options:
1875 - Now NodeFamily and MyFamily config options allow spaces in
1876 identity fingerprints, so it's easier to paste them in.
1877 Suggested by Lucky Green.
1878 - Allow ports 465 and 587 in the default exit policy again. We had
1879 rejected them in 0.1.0.15, because back in 2005 they were commonly
1880 misconfigured and ended up as spam targets. We hear they are better
1881 locked down these days.
1882 - Make TrackHostExit mappings expire a while after their last use, not
1883 after their creation. Patch from Robert Hogan.
1884 - Add an ExcludeExitNodes option so users can list a set of nodes
1885 that should be be excluded from the exit node position, but
1886 allowed elsewhere. Implements proposal 151.
1887 - New --hush command-line option similar to --quiet. While --quiet
1888 disables all logging to the console on startup, --hush limits the
1889 output to messages of warning and error severity.
1890 - New configure/torrc options (--enable-geoip-stats,
1891 DirRecordUsageByCountry) to record how many IPs we've served
1892 directory info to in each country code, how many status documents
1893 total we've sent to each country code, and what share of the total
1894 directory requests we should expect to see.
1895 - Make outbound DNS packets respect the OutboundBindAddress setting.
1896 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
1897 - Allow separate log levels to be configured for different logging
1898 domains. For example, this allows one to log all notices, warnings,
1899 or errors, plus all memory management messages of level debug or
1900 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
1901 - Update to the "June 3 2009" ip-to-country file.
1903 o Minor features (relays):
1904 - Raise the minimum rate limiting to be a relay from 20000 bytes
1905 to 20480 bytes (aka 20KB/s), to match our documentation. Also
1906 update directory authorities so they always assign the Fast flag
1907 to relays with 20KB/s of capacity. Now people running relays won't
1908 suddenly find themselves not seeing any use, if the network gets
1910 - If we're a relay and we change our IP address, be more verbose
1911 about the reason that made us change. Should help track down
1912 further bugs for relays on dynamic IP addresses.
1913 - Exit servers can now answer resolve requests for ip6.arpa addresses.
1914 - Implement most of Proposal 152: allow specialized servers to permit
1915 single-hop circuits, and clients to use those servers to build
1916 single-hop circuits when using a specialized controller. Patch
1917 from Josh Albrecht. Resolves feature request 768.
1918 - When relays do their initial bandwidth measurement, don't limit
1919 to just our entry guards for the test circuits. Otherwise we tend
1920 to have multiple test circuits going through a single entry guard,
1921 which makes our bandwidth test less accurate. Fixes part of bug 654;
1922 patch contributed by Josh Albrecht.
1924 o Minor features (directory authorities):
1925 - Try not to open more than one descriptor-downloading connection
1926 to an authority at once. This should reduce load on directory
1927 authorities. Fixes bug 366.
1928 - Add cross-certification to newly generated certificates, so that
1929 a signing key is enough information to look up a certificate. Start
1930 serving certificates by <identity digest, signing key digest>
1931 pairs. Implements proposal 157.
1932 - When a directory authority downloads a descriptor that it then
1933 immediately rejects, do not retry downloading it right away. Should
1934 save some bandwidth on authorities. Fix for bug 888. Patch by
1936 - Directory authorities now serve a /tor/dbg-stability.txt URL to
1937 help debug WFU and MTBF calculations.
1938 - In directory authorities' approved-routers files, allow
1939 fingerprints with or without space.
1941 o Minor features (directory mirrors):
1942 - When a download gets us zero good descriptors, do not notify
1943 Tor that new directory information has arrived.
1944 - Servers support a new URL scheme for consensus downloads that
1945 allows the client to specify which authorities are trusted.
1946 The server then only sends the consensus if the client will trust
1947 it. Otherwise a 404 error is sent back. Clients use this
1948 new scheme when the server supports it (meaning it's running
1949 0.2.1.1-alpha or later). Implements proposal 134.
1951 o Minor features (bridges):
1952 - If the bridge config line doesn't specify a port, assume 443.
1953 This makes bridge lines a bit smaller and easier for users to
1955 - If we're using bridges and our network goes away, be more willing
1956 to forgive our bridges and try again when we get an application
1959 o Minor features (hidden services):
1960 - When the client launches an introduction circuit, retry with a
1961 new circuit after 30 seconds rather than 60 seconds.
1962 - Launch a second client-side introduction circuit in parallel
1963 after a delay of 15 seconds (based on work by Christian Wilms).
1964 - Hidden services start out building five intro circuits rather
1965 than three, and when the first three finish they publish a service
1966 descriptor using those. Now we publish our service descriptor much
1967 faster after restart.
1968 - Drop the requirement to have an open dir port for storing and
1969 serving v2 hidden service descriptors.
1971 o Minor features (build and packaging):
1972 - On Linux, use the prctl call to re-enable core dumps when the User
1974 - Try to make sure that the version of Libevent we're running with
1975 is binary-compatible with the one we built with. May address bug
1977 - Add a new --enable-local-appdata configuration switch to change
1978 the default location of the datadir on win32 from APPDATA to
1979 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
1980 entirely. Patch from coderman.
1981 - Build correctly against versions of OpenSSL 0.9.8 or later that
1982 are built without support for deprecated functions.
1983 - On platforms with a maximum syslog string length, truncate syslog
1984 messages to that length ourselves, rather than relying on the
1985 system to do it for us.
1986 - Automatically detect MacOSX versions earlier than 10.4.0, and
1987 disable kqueue from inside Tor when running with these versions.
1988 We previously did this from the startup script, but that was no
1989 help to people who didn't use the startup script. Resolves bug 863.
1990 - Build correctly when configured to build outside the main source
1991 path. Patch from Michael Gold.
1992 - Disable GCC's strict alias optimization by default, to avoid the
1993 likelihood of its introducing subtle bugs whenever our code violates
1994 the letter of C99's alias rules.
1995 - Change the contrib/tor.logrotate script so it makes the new
1996 logs as "_tor:_tor" rather than the default, which is generally
1997 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
1998 - Change our header file guard macros to be less likely to conflict
1999 with system headers. Adam Langley noticed that we were conflicting
2000 with log.h on Android.
2001 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
2002 and stop using a warning that had become unfixably verbose under
2004 - Use a lockfile to make sure that two Tor processes are not
2005 simultaneously running with the same datadir.
2006 - Allow OpenSSL to use dynamic locks if it wants.
2007 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
2009 o Minor features (controllers):
2010 - When generating circuit events with verbose nicknames for
2011 controllers, try harder to look up nicknames for routers on a
2012 circuit. (Previously, we would look in the router descriptors we had
2013 for nicknames, but not in the consensus.) Partial fix for bug 941.
2014 - New controller event NEWCONSENSUS that lists the networkstatus
2015 lines for every recommended relay. Now controllers like Torflow
2016 can keep up-to-date on which relays they should be using.
2017 - New controller event "clients_seen" to report a geoip-based summary
2018 of which countries we've seen clients from recently. Now controllers
2019 like Vidalia can show bridge operators that they're actually making
2021 - Add a 'getinfo status/clients-seen' controller command, in case
2022 controllers want to hear clients_seen events but connect late.
2023 - New CONSENSUS_ARRIVED event to note when a new consensus has
2024 been fetched and validated.
2025 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
2026 controllers to prevent SIGHUP from reloading the configuration.
2028 - Return circuit purposes in response to GETINFO circuit-status.
2030 - Serve the latest v3 networkstatus consensus via the control
2031 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
2032 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
2033 controller can query our current bootstrap state in case it attaches
2034 partway through and wants to catch up.
2035 - Provide circuit purposes along with circuit events to the controller.
2037 o Minor features (tools):
2038 - Do not have tor-resolve automatically refuse all .onion addresses;
2039 if AutomapHostsOnResolve is set in your torrc, this will work fine.
2040 - Add a -p option to tor-resolve for specifying the SOCKS port: some
2041 people find host:port too confusing.
2042 - Print the SOCKS5 error message string as well as the error code
2043 when a tor-resolve request fails. Patch from Jacob.
2045 o Minor bugfixes (memory and resource management):
2046 - Clients no longer cache certificates for authorities they do not
2047 recognize. Bugfix on 0.2.0.9-alpha.
2048 - Do not use C's stdio library for writing to log files. This will
2049 improve logging performance by a minute amount, and will stop
2050 leaking fds when our disk is full. Fixes bug 861.
2051 - Stop erroneous use of O_APPEND in cases where we did not in fact
2052 want to re-seek to the end of a file before every last write().
2053 - Fix a small alignment and memory-wasting bug on buffer chunks.
2055 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
2056 to avoid unused RAM in buffer chunks and memory pools.
2057 - Reduce the default smartlist size from 32 to 16; it turns out that
2058 most smartlists hold around 8-12 elements tops.
2059 - Make dumpstats() log the fullness and size of openssl-internal
2061 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
2062 patch to their OpenSSL, turn it on to save memory on servers. This
2063 patch will (with any luck) get included in a mainline distribution
2065 - Fix a memory leak when v3 directory authorities load their keys
2066 and cert from disk. Bugfix on 0.2.0.1-alpha.
2067 - Stop using malloc_usable_size() to use more area than we had
2068 actually allocated: it was safe, but made valgrind really unhappy.
2069 - Make the assert_circuit_ok() function work correctly on circuits that
2070 have already been marked for close.
2071 - Fix uninitialized size field for memory area allocation: may improve
2072 memory performance during directory parsing.
2074 o Minor bugfixes (clients):
2075 - Stop reloading the router list from disk for no reason when we
2076 run out of reachable directory mirrors. Once upon a time reloading
2077 it would set the 'is_running' flag back to 1 for them. It hasn't
2078 done that for a long time.
2079 - When we had picked an exit node for a connection, but marked it as
2080 "optional", and it turned out we had no onion key for the exit,
2081 stop wanting that exit and try again. This situation may not
2082 be possible now, but will probably become feasible with proposal
2083 158. Spotted by rovv. Fixes another case of bug 752.
2084 - Fix a bug in address parsing that was preventing bridges or hidden
2085 service targets from being at IPv6 addresses.
2086 - Do not remove routers as too old if we do not have any consensus
2087 document. Bugfix on 0.2.0.7-alpha.
2088 - When an exit relay resolves a stream address to a local IP address,
2089 do not just keep retrying that same exit relay over and
2090 over. Instead, just close the stream. Addresses bug 872. Bugfix
2091 on 0.2.0.32. Patch from rovv.
2092 - Made Tor a little less aggressive about deleting expired
2093 certificates. Partial fix for bug 854.
2094 - Treat duplicate certificate fetches as failures, so that we do
2095 not try to re-fetch an expired certificate over and over and over.
2096 - Do not say we're fetching a certificate when we'll in fact skip it
2097 because of a pending download.
2098 - If we have correct permissions on $datadir, we complain to stdout
2099 and fail to start. But dangerous permissions on
2100 $datadir/cached-status/ would cause us to open a log and complain
2101 there. Now complain to stdout and fail to start in both cases. Fixes
2102 bug 820, reported by seeess.
2104 o Minor bugfixes (bridges):
2105 - When we made bridge authorities stop serving bridge descriptors over
2106 unencrypted links, we also broke DirPort reachability testing for
2107 bridges. So bridges with a non-zero DirPort were printing spurious
2108 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
2109 - Don't allow a bridge to publish its router descriptor to a
2110 non-bridge directory authority. Fixes part of bug 932.
2111 - When we change to or from being a bridge, reset our counts of
2112 client usage by country. Fixes bug 932.
2114 o Minor bugfixes (relays):
2115 - Log correct error messages for DNS-related network errors on
2117 - Actually return -1 in the error case for read_bandwidth_usage().
2118 Harmless bug, since we currently don't care about the return value
2119 anywhere. Bugfix on 0.2.0.9-alpha.
2120 - Provide a more useful log message if bug 977 (related to buffer
2121 freelists) ever reappears, and do not crash right away.
2122 - We were already rejecting relay begin cells with destination port
2123 of 0. Now also reject extend cells with destination port or address
2124 of 0. Suggested by lark.
2125 - When we can't transmit a DNS request due to a network error, retry
2126 it after a while, and eventually transmit a failing response to
2127 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
2128 - Solve a bug that kept hardware crypto acceleration from getting
2129 enabled when accounting was turned on. Fixes bug 907. Bugfix on
2131 - When a canonical connection appears later in our internal list
2132 than a noncanonical one for a given OR ID, always use the
2133 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
2135 - Avoid some nasty corner cases in the logic for marking connections
2136 as too old or obsolete or noncanonical for circuits. Partial
2138 - Fix another interesting corner-case of bug 891 spotted by rovv:
2139 Previously, if two hosts had different amounts of clock drift, and
2140 one of them created a new connection with just the wrong timing,
2141 the other might decide to deprecate the new connection erroneously.
2142 Bugfix on 0.1.1.13-alpha.
2143 - If one win32 nameserver fails to get added, continue adding the
2144 rest, and don't automatically fail.
2145 - Fix a bug where an unreachable relay would establish enough
2146 reachability testing circuits to do a bandwidth test -- if
2147 we already have a connection to the middle hop of the testing
2148 circuit, then it could establish the last hop by using the existing
2149 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
2150 circuits no longer use entry guards in 0.2.1.3-alpha.
2152 o Minor bugfixes (directory authorities):
2153 - Limit uploaded directory documents to be 16M rather than 500K.
2154 The directory authorities were refusing v3 consensus votes from
2155 other authorities, since the votes are now 504K. Fixes bug 959;
2156 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
2157 - Directory authorities should never send a 503 "busy" response to
2158 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
2160 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
2161 headers. Bugfix on 0.2.0.10-alpha.
2163 o Minor bugfixes (hidden services):
2164 - When we can't find an intro key for a v2 hidden service descriptor,
2165 fall back to the v0 hidden service descriptor and log a bug message.
2166 Workaround for bug 1024.
2167 - In very rare situations new hidden service descriptors were
2168 published earlier than 30 seconds after the last change to the
2169 service. (We currently think that a hidden service descriptor
2170 that's been stable for 30 seconds is worth publishing.)
2171 - If a hidden service sends us an END cell, do not consider
2172 retrying the connection; just close it. Patch from rovv.
2173 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
2174 service directories if they have no advertised dir port. Bugfix
2177 o Minor bugfixes (tools):
2178 - In the torify(1) manpage, mention that tsocks will leak your
2181 o Minor bugfixes (controllers):
2182 - If the controller claimed responsibility for a stream, but that
2183 stream never finished making its connection, it would live
2184 forever in circuit_wait state. Now we close it after SocksTimeout
2185 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
2186 - Make DNS resolved controller events into "CLOSED", not
2187 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
2189 - The control port would close the connection before flushing long
2190 replies, such as the network consensus, if a QUIT command was issued
2191 before the reply had completed. Now, the control port flushes all
2192 pending replies before closing the connection. Also fix a spurious
2193 warning when a QUIT command is issued after a malformed or rejected
2194 AUTHENTICATE command, but before the connection was closed. Patch
2195 by Marcus Griep. Fixes bugs 1015 and 1016.
2196 - Fix a bug that made stream bandwidth get misreported to the
2199 o Deprecated and removed features:
2200 - The old "tor --version --version" command, which would print out
2201 the subversion "Id" of most of the source files, is now removed. It
2202 turned out to be less useful than we'd expected, and harder to
2204 - RedirectExits has been removed. It was deprecated since
2206 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
2207 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
2208 - Cell pools are now always enabled; --disable-cell-pools is ignored.
2209 - Directory mirrors no longer fetch the v1 directory or
2210 running-routers files. They are obsolete, and nobody asks for them
2211 anymore. This is the first step to making v1 authorities obsolete.
2212 - Take out the TestVia config option, since it was a workaround for
2213 a bug that was fixed in Tor 0.1.1.21.
2214 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
2215 HiddenServiceExcludeNodes as obsolete: they never worked properly,
2216 and nobody seems to be using them. Fixes bug 754. Bugfix on
2217 0.1.0.1-rc. Patch from Christian Wilms.
2218 - Remove all backward-compatibility code for relays running
2219 versions of Tor so old that they no longer work at all on the
2222 o Code simplifications and refactoring:
2223 - Tool-assisted documentation cleanup. Nearly every function or
2224 static variable in Tor should have its own documentation now.
2225 - Rename the confusing or_is_obsolete field to the more appropriate
2226 is_bad_for_new_circs, and move it to or_connection_t where it
2228 - Move edge-only flags from connection_t to edge_connection_t: not
2229 only is this better coding, but on machines of plausible alignment,
2230 it should save 4-8 bytes per connection_t. "Every little bit helps."
2231 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
2232 for consistency; keep old option working for backward compatibility.
2233 - Simplify the code for finding connections to use for a circuit.
2234 - Revise the connection_new functions so that a more typesafe variant
2235 exists. This will work better with Coverity, and let us find any
2236 actual mistakes we're making here.
2237 - Refactor unit testing logic so that dmalloc can be used sensibly
2238 with unit tests to check for memory leaks.
2239 - Move all hidden-service related fields from connection and circuit
2240 structure to substructures: this way they won't eat so much memory.
2241 - Squeeze 2-5% out of client performance (according to oprofile) by
2242 improving the implementation of some policy-manipulation functions.
2243 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
2244 be more efficient. Formerly it was quadratic in the number of
2245 servers; now it should be linear. Fixes bug 509.
2246 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
2247 and n_conn_id_digest fields into a separate structure that's
2248 only needed when the circuit has not yet attached to an n_conn.
2249 - Optimize out calls to time(NULL) that occur for every IO operation,
2250 or for every cell. On systems like Windows where time() is a
2251 slow syscall, this fix will be slightly helpful.
2254 Changes in version 0.2.0.35 - 2009-06-24
2256 - Avoid crashing in the presence of certain malformed descriptors.
2257 Found by lark, and by automated fuzzing.
2258 - Fix an edge case where a malicious exit relay could convince a
2259 controller that the client's DNS question resolves to an internal IP
2260 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
2263 - Finally fix the bug where dynamic-IP relays disappear when their
2264 IP address changes: directory mirrors were mistakenly telling
2265 them their old address if they asked via begin_dir, so they
2266 never got an accurate answer about their new address, so they
2267 just vanished after a day. For belt-and-suspenders, relays that
2268 don't set Address in their config now avoid using begin_dir for
2269 all direct connections. Should fix bugs 827, 883, and 900.
2270 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
2271 that would occur on some exit nodes when DNS failures and timeouts
2272 occurred in certain patterns. Fix for bug 957.
2275 - When starting with a cache over a few days old, do not leak
2276 memory for the obsolete router descriptors in it. Bugfix on
2277 0.2.0.33; fixes bug 672.
2278 - Hidden service clients didn't use a cached service descriptor that
2279 was older than 15 minutes, but wouldn't fetch a new one either,
2280 because there was already one in the cache. Now, fetch a v2
2281 descriptor unless the same descriptor was added to the cache within
2282 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
2285 Changes in version 0.2.0.34 - 2009-02-08
2286 Tor 0.2.0.34 features several more security-related fixes. You should
2287 upgrade, especially if you run an exit relay (remote crash) or a
2288 directory authority (remote infinite loop), or you're on an older
2289 (pre-XP) or not-recently-patched Windows (remote exploit).
2291 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
2292 have many known flaws, and nobody should be using them. You should
2293 upgrade. If you're using a Linux or BSD and its packages are obsolete,
2294 stop using those packages and upgrade anyway.
2297 - Fix an infinite-loop bug on handling corrupt votes under certain
2298 circumstances. Bugfix on 0.2.0.8-alpha.
2299 - Fix a temporary DoS vulnerability that could be performed by
2300 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
2301 - Avoid a potential crash on exit nodes when processing malformed
2302 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
2303 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
2304 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
2307 - Fix compilation on systems where time_t is a 64-bit integer.
2308 Patch from Matthias Drochner.
2309 - Don't consider expiring already-closed client connections. Fixes
2310 bug 893. Bugfix on 0.0.2pre20.
2313 Changes in version 0.2.0.33 - 2009-01-21
2314 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
2315 useful to users. It also finally fixes a bug where a relay or client
2316 that's been off for many days would take a long time to bootstrap.
2318 This update also fixes an important security-related bug reported by
2319 Ilja van Sprundel. You should upgrade. (We'll send out more details
2320 about the bug once people have had some time to upgrade.)
2323 - Fix a heap-corruption bug that may be remotely triggerable on
2324 some platforms. Reported by Ilja van Sprundel.
2327 - When a stream at an exit relay is in state "resolving" or
2328 "connecting" and it receives an "end" relay cell, the exit relay
2329 would silently ignore the end cell and not close the stream. If
2330 the client never closes the circuit, then the exit relay never
2331 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
2333 - When sending CREATED cells back for a given circuit, use a 64-bit
2334 connection ID to find the right connection, rather than an addr:port
2335 combination. Now that we can have multiple OR connections between
2336 the same ORs, it is no longer possible to use addr:port to uniquely
2337 identify a connection.
2338 - Bridge relays that had DirPort set to 0 would stop fetching
2339 descriptors shortly after startup, and then briefly resume
2340 after a new bandwidth test and/or after publishing a new bridge
2341 descriptor. Bridge users that try to bootstrap from them would
2342 get a recent networkstatus but would get descriptors from up to
2343 18 hours earlier, meaning most of the descriptors were obsolete
2344 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
2345 - Prevent bridge relays from serving their 'extrainfo' document
2346 to anybody who asks, now that extrainfo docs include potentially
2347 sensitive aggregated client geoip summaries. Bugfix on
2349 - If the cached networkstatus consensus is more than five days old,
2350 discard it rather than trying to use it. In theory it could be
2351 useful because it lists alternate directory mirrors, but in practice
2352 it just means we spend many minutes trying directory mirrors that
2353 are long gone from the network. Also discard router descriptors as
2354 we load them if they are more than five days old, since the onion
2355 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
2358 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
2359 could make gcc generate non-functional binary search code. Bugfix
2361 - Build correctly on platforms without socklen_t.
2362 - Compile without warnings on solaris.
2363 - Avoid potential crash on internal error during signature collection.
2364 Fixes bug 864. Patch from rovv.
2365 - Correct handling of possible malformed authority signing key
2366 certificates with internal signature types. Fixes bug 880.
2367 Bugfix on 0.2.0.3-alpha.
2368 - Fix a hard-to-trigger resource leak when logging credential status.
2370 - When we can't initialize DNS because the network is down, do not
2371 automatically stop Tor from starting. Instead, we retry failed
2372 dns_init() every 10 minutes, and change the exit policy to reject
2373 *:* until one succeeds. Fixes bug 691.
2374 - Use 64 bits instead of 32 bits for connection identifiers used with
2375 the controller protocol, to greatly reduce risk of identifier reuse.
2376 - When we're choosing an exit node for a circuit, and we have
2377 no pending streams, choose a good general exit rather than one that
2378 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
2379 - Fix another case of assuming, when a specific exit is requested,
2380 that we know more than the user about what hosts it allows.
2381 Fixes one case of bug 752. Patch from rovv.
2382 - Clip the MaxCircuitDirtiness config option to a minimum of 10
2383 seconds. Warn the user if lower values are given in the
2384 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
2385 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
2386 user if lower values are given in the configuration. Bugfix on
2387 0.1.1.17-rc. Patch by Sebastian.
2388 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
2389 the cache because we already had a v0 descriptor with the same ID.
2390 Bugfix on 0.2.0.18-alpha.
2391 - Fix a race condition when freeing keys shared between main thread
2392 and CPU workers that could result in a memory leak. Bugfix on
2393 0.1.0.1-rc. Fixes bug 889.
2394 - Send a valid END cell back when a client tries to connect to a
2395 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
2396 840. Patch from rovv.
2397 - Check which hops rendezvous stream cells are associated with to
2398 prevent possible guess-the-streamid injection attacks from
2399 intermediate hops. Fixes another case of bug 446. Based on patch
2401 - If a broken client asks a non-exit router to connect somewhere,
2402 do not even do the DNS lookup before rejecting the connection.
2403 Fixes another case of bug 619. Patch from rovv.
2404 - When a relay gets a create cell it can't decrypt (e.g. because it's
2405 using the wrong onion key), we were dropping it and letting the
2406 client time out. Now actually answer with a destroy cell. Fixes
2407 bug 904. Bugfix on 0.0.2pre8.
2409 o Minor bugfixes (hidden services):
2410 - Do not throw away existing introduction points on SIGHUP. Bugfix on
2411 0.0.6pre1. Patch by Karsten. Fixes bug 874.
2414 - Report the case where all signatures in a detached set are rejected
2415 differently than the case where there is an error handling the
2417 - When we realize that another process has modified our cached
2418 descriptors, print out a more useful error message rather than
2419 triggering an assertion. Fixes bug 885. Patch from Karsten.
2420 - Implement the 0x20 hack to better resist DNS poisoning: set the
2421 case on outgoing DNS requests randomly, and reject responses that do
2422 not match the case correctly. This logic can be disabled with the
2423 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
2424 of servers that do not reliably preserve case in replies. See
2425 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
2427 - Check DNS replies for more matching fields to better resist DNS
2429 - Never use OpenSSL compression: it wastes RAM and CPU trying to
2430 compress cells, which are basically all encrypted, compressed, or
2434 Changes in version 0.2.0.32 - 2008-11-20
2435 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
2436 packages (and maybe other packages) noticed by Theo de Raadt, fixes
2437 a smaller security flaw that might allow an attacker to access local
2438 services, further improves hidden service performance, and fixes a
2439 variety of other issues.
2442 - The "User" and "Group" config options did not clear the
2443 supplementary group entries for the Tor process. The "User" option
2444 is now more robust, and we now set the groups to the specified
2445 user's primary group. The "Group" option is now ignored. For more
2446 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
2447 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
2448 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
2449 - The "ClientDNSRejectInternalAddresses" config option wasn't being
2450 consistently obeyed: if an exit relay refuses a stream because its
2451 exit policy doesn't allow it, we would remember what IP address
2452 the relay said the destination address resolves to, even if it's
2453 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
2456 - Fix a DOS opportunity during the voting signature collection process
2457 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
2459 o Major bugfixes (hidden services):
2460 - When fetching v0 and v2 rendezvous service descriptors in parallel,
2461 we were failing the whole hidden service request when the v0
2462 descriptor fetch fails, even if the v2 fetch is still pending and
2463 might succeed. Similarly, if the last v2 fetch fails, we were
2464 failing the whole hidden service request even if a v0 fetch is
2465 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
2466 - When extending a circuit to a hidden service directory to upload a
2467 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
2468 requests failed, because the router descriptor has not been
2469 downloaded yet. In these cases, do not attempt to upload the
2470 rendezvous descriptor, but wait until the router descriptor is
2471 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
2472 descriptor from a hidden service directory for which the router
2473 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
2477 - Fix several infrequent memory leaks spotted by Coverity.
2478 - When testing for libevent functions, set the LDFLAGS variable
2479 correctly. Found by Riastradh.
2480 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
2481 bootstrapping with tunneled directory connections. Bugfix on
2482 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
2483 - When asked to connect to A.B.exit:80, if we don't know the IP for A
2484 and we know that server B rejects most-but-not all connections to
2485 port 80, we would previously reject the connection. Now, we assume
2486 the user knows what they were asking for. Fixes bug 752. Bugfix
2487 on 0.0.9rc5. Diagnosed by BarkerJr.
2488 - If we overrun our per-second write limits a little, count this as
2489 having used up our write allocation for the second, and choke
2490 outgoing directory writes. Previously, we had only counted this when
2491 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
2492 Bugfix on 0.2.0.x (??).
2493 - Remove the old v2 directory authority 'lefkada' from the default
2494 list. It has been gone for many months.
2495 - Stop doing unaligned memory access that generated bus errors on
2496 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
2497 - Make USR2 log-level switch take effect immediately. Bugfix on
2500 o Minor bugfixes (controller):
2501 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
2502 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
2505 Changes in version 0.2.0.31 - 2008-09-03
2506 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
2507 a big bug we're seeing where in rare cases traffic from one Tor stream
2508 gets mixed into another stream, and fixes a variety of smaller issues.
2511 - Make sure that two circuits can never exist on the same connection
2512 with the same circuit ID, even if one is marked for close. This
2513 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
2514 - Relays now reject risky extend cells: if the extend cell includes
2515 a digest of all zeroes, or asks to extend back to the relay that
2516 sent the extend cell, tear down the circuit. Ideas suggested
2518 - If not enough of our entry guards are available so we add a new
2519 one, we might use the new one even if it overlapped with the
2520 current circuit's exit relay (or its family). Anonymity bugfix
2521 pointed out by rovv.
2524 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
2525 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
2526 - Correctly detect the presence of the linux/netfilter_ipv4.h header
2527 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
2528 - Pick size of default geoip filename string correctly on windows.
2529 Fixes bug 806. Bugfix on 0.2.0.30.
2530 - Make the autoconf script accept the obsolete --with-ssl-dir
2531 option as an alias for the actually-working --with-openssl-dir
2532 option. Fix the help documentation to recommend --with-openssl-dir.
2533 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
2534 - When using the TransPort option on OpenBSD, and using the User
2535 option to change UID and drop privileges, make sure to open
2536 /dev/pf before dropping privileges. Fixes bug 782. Patch from
2537 Christopher Davis. Bugfix on 0.1.2.1-alpha.
2538 - Try to attach connections immediately upon receiving a RENDEZVOUS2
2539 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
2540 on the client side when connecting to a hidden service. Bugfix
2541 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
2542 - When closing an application-side connection because its circuit is
2543 getting torn down, generate the stream event correctly. Bugfix on
2544 0.1.2.x. Anonymous patch.
2547 Changes in version 0.2.0.30 - 2008-07-15
2548 This new stable release switches to a more efficient directory
2549 distribution design, adds features to make connections to the Tor
2550 network harder to block, allows Tor to act as a DNS proxy, adds separate
2551 rate limiting for relayed traffic to make it easier for clients to
2552 become relays, fixes a variety of potential anonymity problems, and
2553 includes the usual huge pile of other features and bug fixes.
2555 o New v3 directory design:
2556 - Tor now uses a new way to learn about and distribute information
2557 about the network: the directory authorities vote on a common
2558 network status document rather than each publishing their own
2559 opinion. Now clients and caches download only one networkstatus
2560 document to bootstrap, rather than downloading one for each
2561 authority. Clients only download router descriptors listed in
2562 the consensus. Implements proposal 101; see doc/spec/dir-spec.txt
2564 - Set up moria1, tor26, and dizum as v3 directory authorities
2565 in addition to being v2 authorities. Also add three new ones:
2566 ides (run by Mike Perry), gabelmoo (run by Karsten Loesing), and
2567 dannenberg (run by CCC).
2568 - Switch to multi-level keys for directory authorities: now their
2569 long-term identity key can be kept offline, and they periodically
2570 generate a new signing key. Clients fetch the "key certificates"
2571 to keep up to date on the right keys. Add a standalone tool
2572 "tor-gencert" to generate key certificates. Implements proposal 103.
2573 - Add a new V3AuthUseLegacyKey config option to make it easier for
2574 v3 authorities to change their identity keys if another bug like
2575 Debian's OpenSSL RNG flaw appears.
2576 - Authorities and caches fetch the v2 networkstatus documents
2577 less often, now that v3 is recommended.
2579 o Make Tor connections stand out less on the wire:
2580 - Use an improved TLS handshake designed by Steven Murdoch in proposal
2581 124, as revised in proposal 130. The new handshake is meant to
2582 be harder for censors to fingerprint, and it adds the ability
2583 to detect certain kinds of man-in-the-middle traffic analysis
2584 attacks. The new handshake format includes version negotiation for
2585 OR connections as described in proposal 105, which will allow us
2586 to improve Tor's link protocol more safely in the future.
2587 - Enable encrypted directory connections by default for non-relays,
2588 so censor tools that block Tor directory connections based on their
2589 plaintext patterns will no longer work. This means Tor works in
2590 certain censored countries by default again.
2591 - Stop including recognizeable strings in the commonname part of
2592 Tor's x509 certificates.
2594 o Implement bridge relays:
2595 - Bridge relays (or "bridges" for short) are Tor relays that aren't
2596 listed in the main Tor directory. Since there is no complete public
2597 list of them, even an ISP that is filtering connections to all the
2598 known Tor relays probably won't be able to block all the bridges.
2599 See doc/design-paper/blocking.pdf and proposal 125 for details.
2600 - New config option BridgeRelay that specifies you want to be a
2601 bridge relay rather than a normal relay. When BridgeRelay is set
2602 to 1, then a) you cache dir info even if your DirPort ins't on,
2603 and b) the default for PublishServerDescriptor is now "bridge"
2604 rather than "v2,v3".
2605 - New config option "UseBridges 1" for clients that want to use bridge
2606 relays instead of ordinary entry guards. Clients then specify
2607 bridge relays by adding "Bridge" lines to their config file. Users
2608 can learn about a bridge relay either manually through word of
2609 mouth, or by one of our rate-limited mechanisms for giving out
2610 bridge addresses without letting an attacker easily enumerate them
2611 all. See https://www.torproject.org/bridges for details.
2612 - Bridge relays behave like clients with respect to time intervals
2613 for downloading new v3 consensus documents -- otherwise they
2614 stand out. Bridge users now wait until the end of the interval,
2615 so their bridge relay will be sure to have a new consensus document.
2617 o Implement bridge directory authorities:
2618 - Bridge authorities are like normal directory authorities, except
2619 they don't serve a list of known bridges. Therefore users that know
2620 a bridge's fingerprint can fetch a relay descriptor for that bridge,
2621 including fetching updates e.g. if the bridge changes IP address,
2622 yet an attacker can't just fetch a list of all the bridges.
2623 - Set up Tonga as the default bridge directory authority.
2624 - Bridge authorities refuse to serve bridge descriptors or other
2625 bridge information over unencrypted connections (that is, when
2626 responding to direct DirPort requests rather than begin_dir cells.)
2627 - Bridge directory authorities do reachability testing on the
2628 bridges they know. They provide router status summaries to the
2629 controller via "getinfo ns/purpose/bridge", and also dump summaries
2630 to a file periodically, so we can keep internal stats about which
2631 bridges are functioning.
2632 - If bridge users set the UpdateBridgesFromAuthority config option,
2633 but the digest they ask for is a 404 on the bridge authority,
2634 they fall back to contacting the bridge directly.
2635 - Bridges always use begin_dir to publish their server descriptor to
2636 the bridge authority using an anonymous encrypted tunnel.
2637 - Early work on a "bridge community" design: if bridge authorities set
2638 the BridgePassword config option, they will serve a snapshot of
2639 known bridge routerstatuses from their DirPort to anybody who
2640 knows that password. Unset by default.
2641 - Tor now includes an IP-to-country GeoIP file, so bridge relays can
2642 report sanitized aggregated summaries in their extra-info documents
2643 privately to the bridge authority, listing which countries are
2644 able to reach them. We hope this mechanism will let us learn when
2645 certain countries start trying to block bridges.
2646 - Bridge authorities write bridge descriptors to disk, so they can
2647 reload them after a reboot. They can also export the descriptors
2648 to other programs, so we can distribute them to blocked users via
2649 the BridgeDB interface, e.g. via https://bridges.torproject.org/
2650 and bridges@torproject.org.
2652 o Tor can be a DNS proxy:
2653 - The new client-side DNS proxy feature replaces the need for
2654 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
2655 for DNS requests on port 9999, use the Tor network to resolve them
2656 anonymously, and send the reply back like a regular DNS server.
2657 The code still only implements a subset of DNS.
2658 - Add a new AutomapHostsOnResolve option: when it is enabled, any
2659 resolve request for hosts matching a given pattern causes Tor to
2660 generate an internal virtual address mapping for that host. This
2661 allows DNSPort to work sensibly with hidden service users. By
2662 default, .exit and .onion addresses are remapped; the list of
2663 patterns can be reconfigured with AutomapHostsSuffixes.
2664 - Add an "-F" option to tor-resolve to force a resolve for a .onion
2665 address. Thanks to the AutomapHostsOnResolve option, this is no
2666 longer a completely silly thing to do.
2668 o Major features (relay usability):
2669 - New config options RelayBandwidthRate and RelayBandwidthBurst:
2670 a separate set of token buckets for relayed traffic. Right now
2671 relayed traffic is defined as answers to directory requests, and
2672 OR connections that don't have any local circuits on them. See
2673 proposal 111 for details.
2674 - Create listener connections before we setuid to the configured
2675 User and Group. Now non-Windows users can choose port values
2676 under 1024, start Tor as root, and have Tor bind those ports
2677 before it changes to another UID. (Windows users could already
2679 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
2680 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
2681 on "vserver" accounts. Patch from coderman.
2683 o Major features (directory authorities):
2684 - Directory authorities track weighted fractional uptime and weighted
2685 mean-time-between failures for relays. WFU is suitable for deciding
2686 whether a node is "usually up", while MTBF is suitable for deciding
2687 whether a node is "likely to stay up." We need both, because
2688 "usually up" is a good requirement for guards, while "likely to
2689 stay up" is a good requirement for long-lived connections.
2690 - Directory authorities use a new formula for selecting which relays
2691 to advertise as Guards: they must be in the top 7/8 in terms of
2692 how long we have known about them, and above the median of those
2693 nodes in terms of weighted fractional uptime.
2694 - Directory authorities use a new formula for selecting which relays
2695 to advertise as Stable: when we have 4 or more days of data, use
2696 median measured MTBF rather than median declared uptime. Implements
2698 - Directory authorities accept and serve "extra info" documents for
2699 routers. Routers now publish their bandwidth-history lines in the
2700 extra-info docs rather than the main descriptor. This step saves
2701 60% (!) on compressed router descriptor downloads. Servers upload
2702 extra-info docs to any authority that accepts them; directory
2703 authorities now allow multiple router descriptors and/or extra
2704 info documents to be uploaded in a single go. Authorities, and
2705 caches that have been configured to download extra-info documents,
2706 download them as needed. Implements proposal 104.
2707 - Authorities now list relays who have the same nickname as
2708 a different named relay, but list them with a new flag:
2709 "Unnamed". Now we can make use of relays that happen to pick the
2710 same nickname as a server that registered two years ago and then
2711 disappeared. Implements proposal 122.
2712 - Store routers in a file called cached-descriptors instead of in
2713 cached-routers. Initialize cached-descriptors from cached-routers
2714 if the old format is around. The new format allows us to store
2715 annotations along with descriptors, to record the time we received
2716 each descriptor, its source, and its purpose: currently one of
2717 general, controller, or bridge.
2719 o Major features (other):
2720 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
2721 Tor can warn and/or refuse connections to ports commonly used with
2722 vulnerable-plaintext protocols. Currently we warn on ports 23,
2723 109, 110, and 143, but we don't reject any. Based on proposal 129
2724 by Kevin Bauer and Damon McCoy.
2725 - Integrate Karsten Loesing's Google Summer of Code project to publish
2726 hidden service descriptors on a set of redundant relays that are a
2727 function of the hidden service address. Now we don't have to rely
2728 on three central hidden service authorities for publishing and
2729 fetching every hidden service descriptor. Implements proposal 114.
2730 - Allow tunnelled directory connections to ask for an encrypted
2731 "begin_dir" connection or an anonymized "uses a full Tor circuit"
2732 connection independently. Now we can make anonymized begin_dir
2733 connections for (e.g.) more secure hidden service posting and
2736 o Major bugfixes (crashes and assert failures):
2737 - Stop imposing an arbitrary maximum on the number of file descriptors
2738 used for busy servers. Bug reported by Olaf Selke; patch from
2740 - Avoid possible failures when generating a directory with routers
2741 with over-long versions strings, or too many flags set.
2742 - Fix a rare assert error when we're closing one of our threads:
2743 use a mutex to protect the list of logs, so we never write to the
2744 list as it's being freed. Fixes the very rare bug 575, which is
2745 kind of the revenge of bug 222.
2746 - Avoid segfault in the case where a badly behaved v2 versioning
2747 directory sends a signed networkstatus with missing client-versions.
2748 - When we hit an EOF on a log (probably because we're shutting down),
2749 don't try to remove the log from the list: just mark it as
2750 unusable. (Bulletproofs against bug 222.)
2752 o Major bugfixes (code security fixes):
2753 - Detect size overflow in zlib code. Reported by Justin Ferguson and
2755 - Rewrite directory tokenization code to never run off the end of
2756 a string. Fixes bug 455. Patch from croup.
2757 - Be more paranoid about overwriting sensitive memory on free(),
2758 as a defensive programming tactic to ensure forward secrecy.
2760 o Major bugfixes (anonymity fixes):
2761 - Reject requests for reverse-dns lookup of names that are in
2762 a private address space. Patch from lodger.
2763 - Never report that we've used more bandwidth than we're willing to
2764 relay: it leaks how much non-relay traffic we're using. Resolves
2766 - As a client, do not believe any server that tells us that an
2767 address maps to an internal address space.
2768 - Warn about unsafe ControlPort configurations.
2769 - Directory authorities now call routers Fast if their bandwidth is
2770 at least 100KB/s, and consider their bandwidth adequate to be a
2771 Guard if it is at least 250KB/s, no matter the medians. This fix
2772 complements proposal 107.
2773 - Directory authorities now never mark more than 2 servers per IP as
2774 Valid and Running (or 5 on addresses shared by authorities).
2775 Implements proposal 109, by Kevin Bauer and Damon McCoy.
2776 - If we're a relay, avoid picking ourselves as an introduction point,
2777 a rendezvous point, or as the final hop for internal circuits. Bug
2778 reported by taranis and lodger.
2779 - Exit relays that are used as a client can now reach themselves
2780 using the .exit notation, rather than just launching an infinite
2781 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
2782 - Fix a bug where, when we were choosing the 'end stream reason' to
2783 put in our relay end cell that we send to the exit relay, Tor
2784 clients on Windows were sometimes sending the wrong 'reason'. The
2785 anonymity problem is that exit relays may be able to guess whether
2786 the client is running Windows, thus helping partition the anonymity
2787 set. Down the road we should stop sending reasons to exit relays,
2788 or otherwise prevent future versions of this bug.
2789 - Only update guard status (usable / not usable) once we have
2790 enough directory information. This was causing us to discard all our
2791 guards on startup if we hadn't been running for a few weeks. Fixes
2793 - When our directory information has been expired for a while, stop
2794 being willing to build circuits using it. Fixes bug 401.
2796 o Major bugfixes (peace of mind for relay operators)
2797 - Non-exit relays no longer answer "resolve" relay cells, so they
2798 can't be induced to do arbitrary DNS requests. (Tor clients already
2799 avoid using non-exit relays for resolve cells, but now servers
2800 enforce this too.) Fixes bug 619. Patch from lodger.
2801 - When we setconf ClientOnly to 1, close any current OR and Dir
2802 listeners. Reported by mwenge.
2804 o Major bugfixes (other):
2805 - If we only ever used Tor for hidden service lookups or posts, we
2806 would stop building circuits and start refusing connections after
2807 24 hours, since we falsely believed that Tor was dormant. Reported
2809 - Add a new __HashedControlSessionPassword option for controllers
2810 to use for one-off session password hashes that shouldn't get
2811 saved to disk by SAVECONF --- Vidalia users were accumulating a
2812 pile of HashedControlPassword lines in their torrc files, one for
2813 each time they had restarted Tor and then clicked Save. Make Tor
2814 automatically convert "HashedControlPassword" to this new option but
2815 only when it's given on the command line. Partial fix for bug 586.
2816 - Patch from "Andrew S. Lists" to catch when we contact a directory
2817 mirror at IP address X and he says we look like we're coming from
2818 IP address X. Otherwise this would screw up our address detection.
2819 - Reject uploaded descriptors and extrainfo documents if they're
2820 huge. Otherwise we'll cache them all over the network and it'll
2821 clog everything up. Suggested by Aljosha Judmayer.
2822 - When a hidden service was trying to establish an introduction point,
2823 and Tor *did* manage to reuse one of the preemptively built
2824 circuits, it didn't correctly remember which one it used,
2825 so it asked for another one soon after, until there were no
2826 more preemptive circuits, at which point it launched one from
2827 scratch. Bugfix on 0.0.9.x.
2829 o Rate limiting and load balancing improvements:
2830 - When we add data to a write buffer in response to the data on that
2831 write buffer getting low because of a flush, do not consider the
2832 newly added data as a candidate for immediate flushing, but rather
2833 make it wait until the next round of writing. Otherwise, we flush
2834 and refill recursively, and a single greedy TLS connection can
2835 eat all of our bandwidth.
2836 - When counting the number of bytes written on a TLS connection,
2837 look at the BIO actually used for writing to the network, not
2838 at the BIO used (sometimes) to buffer data for the network.
2839 Looking at different BIOs could result in write counts on the
2840 order of ULONG_MAX. Fixes bug 614.
2841 - If we change our MaxAdvertisedBandwidth and then reload torrc,
2842 Tor won't realize it should publish a new relay descriptor. Fixes
2843 bug 688, reported by mfr.
2844 - Avoid using too little bandwidth when our clock skips a few seconds.
2845 - Choose which bridge to use proportional to its advertised bandwidth,
2846 rather than uniformly at random. This should speed up Tor for
2847 bridge users. Also do this for people who set StrictEntryNodes.
2849 o Bootstrapping faster and building circuits more intelligently:
2850 - Fix bug 660 that was preventing us from knowing that we should
2851 preemptively build circuits to handle expected directory requests.
2852 - When we're checking if we have enough dir info for each relay
2853 to begin establishing circuits, make sure that we actually have
2854 the descriptor listed in the consensus, not just any descriptor.
2855 - Correctly notify one-hop connections when a circuit build has
2856 failed. Possible fix for bug 669. Found by lodger.
2857 - Clients now hold circuitless TLS connections open for 1.5 times
2858 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
2859 rebuild a new circuit over them within that timeframe. Previously,
2860 they held them open only for KeepalivePeriod (5 minutes).
2862 o Performance improvements (memory):
2863 - Add OpenBSD malloc code from "phk" as an optional malloc
2864 replacement on Linux: some glibc libraries do very poorly with
2865 Tor's memory allocation patterns. Pass --enable-openbsd-malloc to
2866 ./configure to get the replacement malloc code.
2867 - Switch our old ring buffer implementation for one more like that
2868 used by free Unix kernels. The wasted space in a buffer with 1mb
2869 of data will now be more like 8k than 1mb. The new implementation
2870 also avoids realloc();realloc(); patterns that can contribute to
2871 memory fragmentation.
2872 - Change the way that Tor buffers data that it is waiting to write.
2873 Instead of queueing data cells in an enormous ring buffer for each
2874 client->OR or OR->OR connection, we now queue cells on a separate
2875 queue for each circuit. This lets us use less slack memory, and
2876 will eventually let us be smarter about prioritizing different kinds
2878 - Reference-count and share copies of address policy entries; only 5%
2879 of them were actually distinct.
2880 - Tune parameters for cell pool allocation to minimize amount of
2882 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
2883 for every single inactive connection_t. Free items from the
2884 4k/16k-buffer free lists when they haven't been used for a while.
2885 - Make memory debugging information describe more about history
2886 of cell allocation, so we can help reduce our memory use.
2887 - Be even more aggressive about releasing RAM from small
2888 empty buffers. Thanks to our free-list code, this shouldn't be too
2889 performance-intensive.
2890 - Log malloc statistics from mallinfo() on platforms where it exists.
2891 - Use memory pools to allocate cells with better speed and memory
2892 efficiency, especially on platforms where malloc() is inefficient.
2893 - Add a --with-tcmalloc option to the configure script to link
2894 against tcmalloc (if present). Does not yet search for non-system
2897 o Performance improvements (socket management):
2898 - Count the number of open sockets separately from the number of
2899 active connection_t objects. This will let us avoid underusing
2900 our allocated connection limit.
2901 - We no longer use socket pairs to link an edge connection to an
2902 anonymous directory connection or a DirPort test connection.
2903 Instead, we track the link internally and transfer the data
2904 in-process. This saves two sockets per "linked" connection (at the
2905 client and at the server), and avoids the nasty Windows socketpair()
2907 - We were leaking a file descriptor if Tor started with a zero-length
2908 cached-descriptors file. Patch by "freddy77".
2910 o Performance improvements (CPU use):
2911 - Never walk through the list of logs if we know that no log target
2912 is interested in a given message.
2913 - Call routerlist_remove_old_routers() much less often. This should
2914 speed startup, especially on directory caches.
2915 - Base64 decoding was actually showing up on our profile when parsing
2916 the initial descriptor file; switch to an in-process all-at-once
2917 implementation that's about 3.5x times faster than calling out to
2919 - Use a slightly simpler string hashing algorithm (copying Python's
2920 instead of Java's) and optimize our digest hashing algorithm to take
2921 advantage of 64-bit platforms and to remove some possibly-costly
2923 - When implementing AES counter mode, update only the portions of the
2924 counter buffer that need to change, and don't keep separate
2925 network-order and host-order counters on big-endian hosts (where
2927 - Add an in-place version of aes_crypt() so that we can avoid doing a
2928 needless memcpy() call on each cell payload.
2929 - Use Critical Sections rather than Mutexes for synchronizing threads
2930 on win32; Mutexes are heavier-weight, and designed for synchronizing
2933 o Performance improvements (bandwidth use):
2934 - Don't try to launch new descriptor downloads quite so often when we
2935 already have enough directory information to build circuits.
2936 - Version 1 directories are no longer generated in full. Instead,
2937 authorities generate and serve "stub" v1 directories that list
2938 no servers. This will stop Tor versions 0.1.0.x and earlier from
2939 working, but (for security reasons) nobody should be running those
2941 - Avoid going directly to the directory authorities even if you're a
2942 relay, if you haven't found yourself reachable yet or if you've
2943 decided not to advertise your dirport yet. Addresses bug 556.
2944 - If we've gone 12 hours since our last bandwidth check, and we
2945 estimate we have less than 50KB bandwidth capacity but we could
2946 handle more, do another bandwidth test.
2947 - Support "If-Modified-Since" when answering HTTP requests for
2948 directories, running-routers documents, and v2 and v3 networkstatus
2949 documents. (There's no need to support it for router descriptors,
2950 since those are downloaded by descriptor digest.)
2951 - Stop fetching directory info so aggressively if your DirPort is
2952 on but your ORPort is off; stop fetching v2 dir info entirely.
2953 You can override these choices with the new FetchDirInfoEarly
2956 o Changed config option behavior (features):
2957 - Configuration files now accept C-style strings as values. This
2958 helps encode characters not allowed in the current configuration
2959 file format, such as newline or #. Addresses bug 557.
2960 - Add hidden services and DNSPorts to the list of things that make
2961 Tor accept that it has running ports. Change starting Tor with no
2962 ports from a fatal error to a warning; we might change it back if
2963 this turns out to confuse anybody. Fixes bug 579.
2964 - Make PublishServerDescriptor default to 1, so the default doesn't
2965 have to change as we invent new directory protocol versions.
2966 - Allow people to say PreferTunnelledDirConns rather than
2967 PreferTunneledDirConns, for those alternate-spellers out there.
2968 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
2969 accommodate the growing number of servers that use the default
2970 and are reaching it.
2971 - Make it possible to enable HashedControlPassword and
2972 CookieAuthentication at the same time.
2973 - When a TrackHostExits-chosen exit fails too many times in a row,
2974 stop using it. Fixes bug 437.
2976 o Changed config option behavior (bugfixes):
2977 - Do not read the configuration file when we've only been told to
2978 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
2979 based on patch from Sebastian Hahn.
2980 - Actually validate the options passed to AuthDirReject,
2981 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
2982 - Make "ClientOnly 1" config option disable directory ports too.
2983 - Don't stop fetching descriptors when FetchUselessDescriptors is
2984 set, even if we stop asking for circuits. Bug reported by tup
2986 - Servers used to decline to publish their DirPort if their
2987 BandwidthRate or MaxAdvertisedBandwidth were below a threshold. Now
2988 they look only at BandwidthRate and RelayBandwidthRate.
2989 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
2990 minus 1 byte: the actual maximum declared bandwidth.
2991 - Make "TrackHostExits ." actually work. Bugfix on 0.1.0.x.
2992 - Make the NodeFamilies config option work. (Reported by
2993 lodger -- it has never actually worked, even though we added it
2995 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
2996 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
2998 o New config options:
2999 - New configuration options AuthDirMaxServersPerAddr and
3000 AuthDirMaxServersperAuthAddr to override default maximum number
3001 of servers allowed on a single IP address. This is important for
3002 running a test network on a single host.
3003 - Three new config options (AlternateDirAuthority,
3004 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
3005 user selectively replace the default directory authorities by type,
3006 rather than the all-or-nothing replacement that DirServer offers.
3007 - New config options AuthDirBadDir and AuthDirListBadDirs for
3008 authorities to mark certain relays as "bad directories" in the
3009 networkstatus documents. Also supports the "!baddir" directive in
3010 the approved-routers file.
3011 - New config option V2AuthoritativeDirectory that all v2 directory
3012 authorities must set. This lets v3 authorities choose not to serve
3013 v2 directory information.
3015 o Minor features (other):
3016 - When we're not serving v2 directory information, there is no reason
3017 to actually keep any around. Remove the obsolete files and directory
3018 on startup if they are very old and we aren't going to serve them.
3019 - When we negotiate a v2 link-layer connection (not yet implemented),
3020 accept RELAY_EARLY cells and turn them into RELAY cells if we've
3021 negotiated a v1 connection for their next step. Initial steps for
3023 - When we have no consensus, check FallbackNetworkstatusFile (defaults
3024 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
3025 we can start out knowing some directory caches. We don't ship with
3026 a fallback consensus by default though, because it was making
3027 bootstrapping take too long while we tried many down relays.
3028 - Authorities send back an X-Descriptor-Not-New header in response to
3029 an accepted-but-discarded descriptor upload. Partially implements
3031 - If we find a cached-routers file that's been sitting around for more
3032 than 28 days unmodified, then most likely it's a leftover from
3033 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
3035 - When we (as a cache) download a descriptor because it was listed
3036 in a consensus, remember when the consensus was supposed to expire,
3037 and don't expire the descriptor until then.
3038 - Optionally (if built with -DEXPORTMALLINFO) export the output
3039 of mallinfo via http, as tor/mallinfo.txt. Only accessible
3041 - Tag every guard node in our state file with the version that
3042 we believe added it, or with our own version if we add it. This way,
3043 if a user temporarily runs an old version of Tor and then switches
3044 back to a new one, she doesn't automatically lose her guards.
3045 - When somebody requests a list of statuses or servers, and we have
3046 none of those, return a 404 rather than an empty 200.
3047 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
3049 - Add an HSAuthorityRecordStats option that hidden service authorities
3050 can use to track statistics of overall hidden service usage without
3051 logging information that would be as useful to an attacker.
3052 - Allow multiple HiddenServicePort directives with the same virtual
3053 port; when they occur, the user is sent round-robin to one
3054 of the target ports chosen at random. Partially fixes bug 393 by
3055 adding limited ad-hoc round-robining.
3056 - Revamp file-writing logic so we don't need to have the entire
3057 contents of a file in memory at once before we write to disk. Tor,
3060 o Minor bugfixes (other):
3061 - Alter the code that tries to recover from unhandled write
3062 errors, to not try to flush onto a socket that's given us
3064 - Directory mirrors no longer include a guess at the client's IP
3065 address if the connection appears to be coming from the same /24
3066 network; it was producing too many wrong guesses.
3067 - If we're trying to flush the last bytes on a connection (for
3068 example, when answering a directory request), reset the
3069 time-to-give-up timeout every time we manage to write something
3071 - Reject router descriptors with out-of-range bandwidthcapacity or
3072 bandwidthburst values.
3073 - If we can't expand our list of entry guards (e.g. because we're
3074 using bridges or we have StrictEntryNodes set), don't mark relays
3075 down when they fail a directory request. Otherwise we're too quick
3076 to mark all our entry points down.
3077 - Authorities no longer send back "400 you're unreachable please fix
3078 it" errors to Tor servers that aren't online all the time. We're
3079 supposed to tolerate these servers now.
3080 - Let directory authorities startup even when they can't generate
3081 a descriptor immediately, e.g. because they don't know their
3083 - Correctly enforce that elements of directory objects do not appear
3084 more often than they are allowed to appear.
3085 - Stop allowing hibernating servers to be "stable" or "fast".
3086 - On Windows, we were preventing other processes from reading
3087 cached-routers while Tor was running. (Reported by janbar)
3088 - Check return values from pthread_mutex functions.
3089 - When opening /dev/null in finish_daemonize(), do not pass the
3090 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
3091 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
3093 o Controller features:
3094 - The GETCONF command now escapes and quotes configuration values
3095 that don't otherwise fit into the torrc file.
3096 - The SETCONF command now handles quoted values correctly.
3097 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
3098 ask about source, timestamp of arrival, purpose, etc. We need
3099 something like this to help Vidalia not do GeoIP lookups on bridge
3101 - Allow multiple HashedControlPassword config lines, to support
3102 multiple controller passwords.
3103 - Accept LF instead of CRLF on controller, since some software has a
3104 hard time generating real Internet newlines.
3105 - Add GETINFO values for the server status events
3106 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
3108 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
3109 GETINFO for Torstat to use until it can switch to using extrainfos.
3110 - New config option CookieAuthFile to choose a new location for the
3111 cookie authentication file, and config option
3112 CookieAuthFileGroupReadable to make it group-readable.
3113 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
3114 match requests to applications. Patch from Robert Hogan.
3115 - Add a RESOLVE command to launch hostname lookups. Original patch
3117 - Add GETINFO status/enough-dir-info to let controllers tell whether
3118 Tor has downloaded sufficient directory information. Patch from Tup.
3119 - You can now use the ControlSocket option to tell Tor to listen for
3120 controller connections on Unix domain sockets on systems that
3121 support them. Patch from Peter Palfrader.
3122 - New "GETINFO address-mappings/*" command to get address mappings
3123 with expiry information. "addr-mappings/*" is now deprecated.
3125 - Add a new config option __DisablePredictedCircuits designed for
3126 use by the controller, when we don't want Tor to build any circuits
3128 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
3129 so we can exit from the middle of the circuit.
3130 - Implement "getinfo status/circuit-established".
3131 - Implement "getinfo status/version/..." so a controller can tell
3132 whether the current version is recommended, and whether any versions
3133 are good, and how many authorities agree. Patch from "shibz".
3134 - Controllers should now specify cache=no or cache=yes when using
3135 the +POSTDESCRIPTOR command.
3136 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
3137 Robert Hogan. Fixes the first part of bug 681.
3138 - When reporting clock skew, and we know that the clock is _at least
3139 as skewed_ as some value, but we don't know the actual value,
3140 report the value as a "minimum skew."
3142 o Controller bugfixes:
3143 - Generate "STATUS_SERVER" events rather than misspelled
3144 "STATUS_SEVER" events. Caught by mwenge.
3145 - Reject controller commands over 1MB in length, so rogue
3146 processes can't run us out of memory.
3147 - Change the behavior of "getinfo status/good-server-descriptor"
3148 so it doesn't return failure when any authority disappears.
3149 - Send NAMESERVER_STATUS messages for a single failed nameserver
3151 - When the DANGEROUS_VERSION controller status event told us we're
3152 running an obsolete version, it used the string "OLD" to describe
3153 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
3154 "OBSOLETE" in both cases.
3155 - Respond to INT and TERM SIGNAL commands before we execute the
3156 signal, in case the signal shuts us down. We had a patch in
3157 0.1.2.1-alpha that tried to do this by queueing the response on
3158 the connection's buffer before shutting down, but that really
3159 isn't the same thing at all. Bug located by Matt Edman.
3160 - Provide DNS expiry times in GMT, not in local time. For backward
3161 compatibility, ADDRMAP events only provide GMT expiry in an extended
3162 field. "GETINFO address-mappings" always does the right thing.
3163 - Use CRLF line endings properly in NS events.
3164 - Make 'getinfo fingerprint' return a 551 error if we're not a
3165 server, so we match what the control spec claims we do. Reported
3167 - Fix a typo in an error message when extendcircuit fails that
3168 caused us to not follow the \r\n-based delimiter protocol. Reported
3170 - When tunneling an encrypted directory connection, and its first
3171 circuit fails, do not leave it unattached and ask the controller
3172 to deal. Fixes the second part of bug 681.
3173 - Treat some 403 responses from directory servers as INFO rather than
3174 WARN-severity events.
3176 o Portability / building / compiling:
3177 - When building with --enable-gcc-warnings, check for whether Apple's
3178 warning "-Wshorten-64-to-32" is available.
3179 - Support compilation to target iPhone; patch from cjacker huang.
3180 To build for iPhone, pass the --enable-iphone option to configure.
3181 - Port Tor to build and run correctly on Windows CE systems, using
3182 the wcecompat library. Contributed by Valerio Lupi.
3183 - Detect non-ASCII platforms (if any still exist) and refuse to
3184 build there: some of our code assumes that 'A' is 65 and so on.
3185 - Clear up some MIPSPro compiler warnings.
3186 - Make autoconf search for libevent, openssl, and zlib consistently.
3187 - Update deprecated macros in configure.in.
3188 - When warning about missing headers, tell the user to let us
3189 know if the compile succeeds anyway, so we can downgrade the
3191 - Include the current subversion revision as part of the version
3192 string: either fetch it directly if we're in an SVN checkout, do
3193 some magic to guess it if we're in an SVK checkout, or use
3194 the last-detected version if we're building from a .tar.gz.
3195 Use this version consistently in log messages.
3196 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
3197 - Read resolv.conf files correctly on platforms where read() returns
3198 partial results on small file reads.
3199 - Build without verbose warnings even on gcc 4.2 and 4.3.
3200 - On Windows, correctly detect errors when listing the contents of
3201 a directory. Fix from lodger.
3202 - Run 'make test' as part of 'make dist', so we stop releasing so
3203 many development snapshots that fail their unit tests.
3204 - Add support to detect Libevent versions in the 1.4.x series
3206 - Add command-line arguments to unit-test executable so that we can
3207 invoke any chosen test from the command line rather than having
3208 to run the whole test suite at once; and so that we can turn on
3209 logging for the unit tests.
3210 - Do not automatically run configure from autogen.sh. This
3211 non-standard behavior tended to annoy people who have built other
3213 - Fix a macro/CPP interaction that was confusing some compilers:
3214 some GCCs don't like #if/#endif pairs inside macro arguments.
3216 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
3217 Fixes bug 704; fix from Steven Murdoch.
3218 - Correctly detect transparent proxy support on Linux hosts that
3219 require in.h to be included before netfilter_ipv4.h. Patch
3222 o Logging improvements:
3223 - When we haven't had any application requests lately, don't bother
3224 logging that we have expired a bunch of descriptors.
3225 - When attempting to open a logfile fails, tell us why.
3226 - Only log guard node status when guard node status has changed.
3227 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
3228 make "INFO" 75% less verbose.
3229 - When SafeLogging is disabled, log addresses along with all TLS
3231 - Report TLS "zero return" case as a "clean close" and "IO error"
3232 as a "close". Stop calling closes "unexpected closes": existing
3233 Tors don't use SSL_close(), so having a connection close without
3234 the TLS shutdown handshake is hardly unexpected.
3235 - When we receive a consensus from the future, warn about skew.
3236 - Make "not enough dir info yet" warnings describe *why* Tor feels
3237 it doesn't have enough directory info yet.
3238 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
3239 consumers. (We already do this on HUP.)
3240 - Give more descriptive well-formedness errors for out-of-range
3241 hidden service descriptor/protocol versions.
3242 - Stop recommending that every server operator send mail to tor-ops.
3243 Resolves bug 597. Bugfix on 0.1.2.x.
3244 - Improve skew reporting: try to give the user a better log message
3245 about how skewed they are, and how much this matters.
3246 - New --quiet command-line option to suppress the default console log.
3247 Good in combination with --hash-password.
3248 - Don't complain that "your server has not managed to confirm that its
3249 ports are reachable" if we haven't been able to build any circuits
3251 - Detect the reason for failing to mmap a descriptor file we just
3252 wrote, and give a more useful log message. Fixes bug 533.
3253 - Always prepend "Bug: " to any log message about a bug.
3254 - When dumping memory usage, list bytes used in buffer memory
3256 - When running with dmalloc, dump more stats on hup and on exit.
3257 - Put a platform string (e.g. "Linux i686") in the startup log
3258 message, so when people paste just their logs, we know if it's
3259 OpenBSD or Windows or what.
3260 - When logging memory usage, break down memory used in buffers by
3262 - When we are reporting the DirServer line we just parsed, we were
3263 logging the second stanza of the key fingerprint, not the first.
3264 - Even though Windows is equally happy with / and \ as path separators,
3265 try to use \ consistently on Windows and / consistently on Unix: it
3266 makes the log messages nicer.
3267 - On OSX, stop warning the user that kqueue support in libevent is
3268 "experimental", since it seems to have worked fine for ages.
3270 o Contributed scripts and tools:
3271 - Update linux-tor-prio.sh script to allow QoS based on the uid of
3272 the Tor process. Patch from Marco Bonetti with tweaks from Mike
3274 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
3275 Unix users an easy way to script their Tor process (e.g. by
3276 adjusting bandwidth based on the time of the day).
3277 - In the exitlist script, only consider the most recently published
3278 server descriptor for each server. Also, when the user requests
3279 a list of servers that _reject_ connections to a given address,
3280 explicitly exclude the IPs that also have servers that accept
3281 connections to that address. Resolves bug 405.
3282 - Include a new contrib/tor-exit-notice.html file that exit relay
3283 operators can put on their website to help reduce abuse queries.
3285 o Newly deprecated features:
3286 - The status/version/num-versioning and status/version/num-concurring
3287 GETINFO controller options are no longer useful in the v3 directory
3288 protocol: treat them as deprecated, and warn when they're used.
3289 - The RedirectExits config option is now deprecated.
3292 - Drop the old code to choke directory connections when the
3293 corresponding OR connections got full: thanks to the cell queue
3294 feature, OR conns don't get full any more.
3295 - Remove the old "dns worker" server DNS code: it hasn't been default
3296 since 0.1.2.2-alpha, and all the servers are using the new
3298 - Remove the code to generate the oldest (v1) directory format.
3299 - Remove support for the old bw_accounting file: we've been storing
3300 bandwidth accounting information in the state file since
3301 0.1.2.5-alpha. This may result in bandwidth accounting errors
3302 if you try to upgrade from 0.1.1.x or earlier, or if you try to
3303 downgrade to 0.1.1.x or earlier.
3304 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
3305 it, it had no AES, and it hasn't seen any security patches since
3307 - Stop overloading the circuit_t.onionskin field for both "onionskin
3308 from a CREATE cell that we are waiting for a cpuworker to be
3309 assigned" and "onionskin from an EXTEND cell that we are going to
3310 send to an OR as soon as we are connected". Might help with bug 600.
3311 - Remove the tor_strpartition() function: its logic was confused,
3312 and it was only used for one thing that could be implemented far
3314 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
3315 and TorControl.py, as they use the old v0 controller protocol,
3316 and are obsoleted by TorFlow anyway.
3317 - Drop support for v1 rendezvous descriptors, since we never used
3318 them anyway, and the code has probably rotted by now. Based on
3319 patch from Karsten Loesing.
3320 - Stop allowing address masks that do not correspond to bit prefixes.
3321 We have warned about these for a really long time; now it's time
3322 to reject them. (Patch from croup.)
3323 - Remove an optimization in the AES counter-mode code that assumed
3324 that the counter never exceeded 2^68. When the counter can be set
3325 arbitrarily as an IV (as it is by Karsten's new hidden services
3326 code), this assumption no longer holds.
3327 - Disable the SETROUTERPURPOSE controller command: it is now
3331 Changes in version 0.1.2.19 - 2008-01-17
3332 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
3333 exit policy a little bit more conservative so it's safer to run an
3334 exit relay on a home system, and fixes a variety of smaller issues.
3337 - Exit policies now reject connections that are addressed to a
3338 relay's public (external) IP address too, unless
3339 ExitPolicyRejectPrivate is turned off. We do this because too
3340 many relays are running nearby to services that trust them based
3344 - When the clock jumps forward a lot, do not allow the bandwidth
3345 buckets to become negative. Fixes bug 544.
3346 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
3347 on every successful resolve. Reported by Mike Perry.
3348 - Purge old entries from the "rephist" database and the hidden
3349 service descriptor database even when DirPort is zero.
3350 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
3351 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
3352 crashing or mis-answering these requests.
3353 - When we decide to send a 503 response to a request for servers, do
3354 not then also send the server descriptors: this defeats the whole
3355 purpose. Fixes bug 539.
3358 - Changing the ExitPolicyRejectPrivate setting should cause us to
3359 rebuild our server descriptor.
3360 - Fix handling of hex nicknames when answering controller requests for
3361 networkstatus by name, or when deciding whether to warn about
3362 unknown routers in a config option. (Patch from mwenge.)
3363 - Fix a couple of hard-to-trigger autoconf problems that could result
3364 in really weird results on platforms whose sys/types.h files define
3365 nonstandard integer types.
3366 - Don't try to create the datadir when running --verify-config or
3367 --hash-password. Resolves bug 540.
3368 - If we were having problems getting a particular descriptor from the
3369 directory caches, and then we learned about a new descriptor for
3370 that router, we weren't resetting our failure count. Reported
3372 - Although we fixed bug 539 (where servers would send HTTP status 503
3373 responses _and_ send a body too), there are still servers out there
3374 that haven't upgraded. Therefore, make clients parse such bodies
3375 when they receive them.
3376 - Run correctly on systems where rlim_t is larger than unsigned long.
3377 This includes some 64-bit systems.
3378 - Run correctly on platforms (like some versions of OS X 10.5) where
3379 the real limit for number of open files is OPEN_FILES, not rlim_max
3380 from getrlimit(RLIMIT_NOFILES).
3381 - Avoid a spurious free on base64 failure.
3382 - Avoid segfaults on certain complex invocations of
3383 router_get_by_hexdigest().
3384 - Fix rare bug on REDIRECTSTREAM control command when called with no
3385 port set: it could erroneously report an error when none had
3389 Changes in version 0.1.2.18 - 2007-10-28
3390 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
3391 hidden service introduction that were causing huge delays, and a big
3392 bug that was causing some servers to disappear from the network status
3393 lists for a few hours each day.
3395 o Major bugfixes (crashes):
3396 - If a connection is shut down abruptly because of something that
3397 happened inside connection_flushed_some(), do not call
3398 connection_finished_flushing(). Should fix bug 451:
3399 "connection_stop_writing: Assertion conn->write_event failed"
3400 Bugfix on 0.1.2.7-alpha.
3401 - Fix possible segfaults in functions called from
3402 rend_process_relay_cell().
3404 o Major bugfixes (hidden services):
3405 - Hidden services were choosing introduction points uniquely by
3406 hexdigest, but when constructing the hidden service descriptor
3407 they merely wrote the (potentially ambiguous) nickname.
3408 - Clients now use the v2 intro format for hidden service
3409 connections: they specify their chosen rendezvous point by identity
3410 digest rather than by (potentially ambiguous) nickname. These
3411 changes could speed up hidden service connections dramatically.
3413 o Major bugfixes (other):
3414 - Stop publishing a new server descriptor just because we get a
3415 HUP signal. This led (in a roundabout way) to some servers getting
3416 dropped from the networkstatus lists for a few hours each day.
3417 - When looking for a circuit to cannibalize, consider family as well
3418 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
3419 circuit cannibalization).
3420 - When a router wasn't listed in a new networkstatus, we were leaving
3421 the flags for that router alone -- meaning it remained Named,
3422 Running, etc -- even though absence from the networkstatus means
3423 that it shouldn't be considered to exist at all anymore. Now we
3424 clear all the flags for routers that fall out of the networkstatus
3425 consensus. Fixes bug 529.
3428 - Don't try to access (or alter) the state file when running
3429 --list-fingerprint or --verify-config or --hash-password. Resolves
3431 - When generating information telling us how to extend to a given
3432 router, do not try to include the nickname if it is
3433 absent. Resolves bug 467.
3434 - Fix a user-triggerable segfault in expand_filename(). (There isn't
3435 a way to trigger this remotely.)
3436 - When sending a status event to the controller telling it that an
3437 OR address is reachable, set the port correctly. (Previously we
3438 were reporting the dir port.)
3439 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
3440 command. Bugfix on 0.1.2.17.
3441 - When loading bandwidth history, do not believe any information in
3442 the future. Fixes bug 434.
3443 - When loading entry guard information, do not believe any information
3445 - When we have our clock set far in the future and generate an
3446 onion key, then re-set our clock to be correct, we should not stop
3447 the onion key from getting rotated.
3448 - On some platforms, accept() can return a broken address. Detect
3449 this more quietly, and deal accordingly. Fixes bug 483.
3450 - It's not actually an error to find a non-pending entry in the DNS
3451 cache when canceling a pending resolve. Don't log unless stuff
3452 is fishy. Resolves bug 463.
3453 - Don't reset trusted dir server list when we set a configuration
3454 option. Patch from Robert Hogan.
3457 Changes in version 0.1.2.17 - 2007-08-30
3458 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
3459 X bundles. Vidalia 0.0.14 makes authentication required for the
3460 ControlPort in the default configuration, which addresses important
3461 security risks. Everybody who uses Vidalia (or another controller)
3464 In addition, this Tor update fixes major load balancing problems with
3465 path selection, which should speed things up a lot once many people
3468 o Major bugfixes (security):
3469 - We removed support for the old (v0) control protocol. It has been
3470 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
3471 become more of a headache than it's worth.
3473 o Major bugfixes (load balancing):
3474 - When choosing nodes for non-guard positions, weight guards
3475 proportionally less, since they already have enough load. Patch
3477 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
3478 will allow fast Tor servers to get more attention.
3479 - When we're upgrading from an old Tor version, forget our current
3480 guards and pick new ones according to the new weightings. These
3481 three load balancing patches could raise effective network capacity
3482 by a factor of four. Thanks to Mike Perry for measurements.
3484 o Major bugfixes (stream expiration):
3485 - Expire not-yet-successful application streams in all cases if
3486 they've been around longer than SocksTimeout. Right now there are
3487 some cases where the stream will live forever, demanding a new
3488 circuit every 15 seconds. Fixes bug 454; reported by lodger.
3490 o Minor features (controller):
3491 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
3492 is valid before any authentication has been received. It tells
3493 a controller what kind of authentication is expected, and what
3494 protocol is spoken. Implements proposal 119.
3496 o Minor bugfixes (performance):
3497 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
3498 greatly speeding up loading cached-routers from disk on startup.
3499 - Disable sentinel-based debugging for buffer code: we squashed all
3500 the bugs that this was supposed to detect a long time ago, and now
3501 its only effect is to change our buffer sizes from nice powers of
3502 two (which platform mallocs tend to like) to values slightly over
3503 powers of two (which make some platform mallocs sad).
3505 o Minor bugfixes (misc):
3506 - If exit bandwidth ever exceeds one third of total bandwidth, then
3507 use the correct formula to weight exit nodes when choosing paths.
3508 Based on patch from Mike Perry.
3509 - Choose perfectly fairly among routers when choosing by bandwidth and
3510 weighting by fraction of bandwidth provided by exits. Previously, we
3511 would choose with only approximate fairness, and correct ourselves
3512 if we ran off the end of the list.
3513 - If we require CookieAuthentication but we fail to write the
3514 cookie file, we would warn but not exit, and end up in a state
3515 where no controller could authenticate. Now we exit.
3516 - If we require CookieAuthentication, stop generating a new cookie
3517 every time we change any piece of our config.
3518 - Refuse to start with certain directory authority keys, and
3519 encourage people using them to stop.
3520 - Terminate multi-line control events properly. Original patch
3522 - Fix a minor memory leak when we fail to find enough suitable
3523 servers to choose a circuit.
3524 - Stop leaking part of the descriptor when we run into a particularly
3525 unparseable piece of it.
3528 Changes in version 0.1.2.16 - 2007-08-01
3529 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
3530 remote attacker in certain situations to rewrite the user's torrc
3531 configuration file. This can completely compromise anonymity of users
3532 in most configurations, including those running the Vidalia bundles,
3533 TorK, etc. Or worse.
3535 o Major security fixes:
3536 - Close immediately after missing authentication on control port;
3537 do not allow multiple authentication attempts.
3540 Changes in version 0.1.2.15 - 2007-07-17
3541 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
3542 problems, fixes compilation on BSD, and fixes a variety of other
3543 bugs. Everybody should upgrade.
3545 o Major bugfixes (compilation):
3546 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
3548 o Major bugfixes (crashes):
3549 - Try even harder not to dereference the first character after
3550 an mmap(). Reported by lodger.
3551 - Fix a crash bug in directory authorities when we re-number the
3552 routerlist while inserting a new router.
3553 - When the cached-routers file is an even multiple of the page size,
3554 don't run off the end and crash. (Fixes bug 455; based on idea
3556 - Fix eventdns.c behavior on Solaris: It is critical to include
3557 orconfig.h _before_ sys/types.h, so that we can get the expected
3558 definition of _FILE_OFFSET_BITS.
3560 o Major bugfixes (security):
3561 - Fix a possible buffer overrun when using BSD natd support. Bug
3563 - When sending destroy cells from a circuit's origin, don't include
3564 the reason for tearing down the circuit. The spec says we didn't,
3565 and now we actually don't. Reported by lodger.
3566 - Keep streamids from different exits on a circuit separate. This
3567 bug may have allowed other routers on a given circuit to inject
3568 cells into streams. Reported by lodger; fixes bug 446.
3569 - If there's a never-before-connected-to guard node in our list,
3570 never choose any guards past it. This way we don't expand our
3571 guard list unless we need to.
3573 o Minor bugfixes (guard nodes):
3574 - Weight guard selection by bandwidth, so that low-bandwidth nodes
3575 don't get overused as guards.
3577 o Minor bugfixes (directory):
3578 - Correctly count the number of authorities that recommend each
3579 version. Previously, we were under-counting by 1.
3580 - Fix a potential crash bug when we load many server descriptors at
3581 once and some of them make others of them obsolete. Fixes bug 458.
3583 o Minor bugfixes (hidden services):
3584 - Stop tearing down the whole circuit when the user asks for a
3585 connection to a port that the hidden service didn't configure.
3588 o Minor bugfixes (misc):
3589 - On Windows, we were preventing other processes from reading
3590 cached-routers while Tor was running. Reported by janbar.
3591 - Fix a possible (but very unlikely) bug in picking routers by
3592 bandwidth. Add a log message to confirm that it is in fact
3593 unlikely. Patch from lodger.
3594 - Backport a couple of memory leak fixes.
3595 - Backport miscellaneous cosmetic bugfixes.
3598 Changes in version 0.1.2.14 - 2007-05-25
3599 Tor 0.1.2.14 changes the addresses of two directory authorities (this
3600 change especially affects those who serve or use hidden services),
3601 and fixes several other crash- and security-related bugs.
3603 o Directory authority changes:
3604 - Two directory authorities (moria1 and moria2) just moved to new
3605 IP addresses. This change will particularly affect those who serve
3606 or use hidden services.
3608 o Major bugfixes (crashes):
3609 - If a directory server runs out of space in the connection table
3610 as it's processing a begin_dir request, it will free the exit stream
3611 but leave it attached to the circuit, leading to unpredictable
3612 behavior. (Reported by seeess, fixes bug 425.)
3613 - Fix a bug in dirserv_remove_invalid() that would cause authorities
3614 to corrupt memory under some really unlikely scenarios.
3615 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
3616 - Avoid segfaults when reading from mmaped descriptor file. (Reported
3619 o Major bugfixes (security):
3620 - When choosing an entry guard for a circuit, avoid using guards
3621 that are in the same family as the chosen exit -- not just guards
3622 that are exactly the chosen exit. (Reported by lodger.)
3624 o Major bugfixes (resource management):
3625 - If a directory authority is down, skip it when deciding where to get
3626 networkstatus objects or descriptors. Otherwise we keep asking
3627 every 10 seconds forever. Fixes bug 384.
3628 - Count it as a failure if we fetch a valid network-status but we
3629 don't want to keep it. Otherwise we'll keep fetching it and keep
3630 not wanting to keep it. Fixes part of bug 422.
3631 - If all of our dirservers have given us bad or no networkstatuses
3632 lately, then stop hammering them once per minute even when we
3633 think they're failed. Fixes another part of bug 422.
3636 - Actually set the purpose correctly for descriptors inserted with
3638 - When we have k non-v2 authorities in our DirServer config,
3639 we ignored the last k authorities in the list when updating our
3641 - Correctly back-off from requesting router descriptors that we are
3642 having a hard time downloading.
3643 - Read resolv.conf files correctly on platforms where read() returns
3644 partial results on small file reads.
3645 - Don't rebuild the entire router store every time we get 32K of
3646 routers: rebuild it when the journal gets very large, or when
3647 the gaps in the store get very large.
3650 - When routers publish SVN revisions in their router descriptors,
3651 authorities now include those versions correctly in networkstatus
3653 - Warn when using a version of libevent before 1.3b to run a server on
3654 OSX or BSD: these versions interact badly with userspace threads.
3657 Changes in version 0.1.2.13 - 2007-04-24
3658 This release features some major anonymity fixes, such as safer path
3659 selection; better client performance; faster bootstrapping, better
3660 address detection, and better DNS support for servers; write limiting as
3661 well as read limiting to make servers easier to run; and a huge pile of
3662 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
3664 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
3665 of the Freenode IRC network, remembering his patience and vision for
3666 free speech on the Internet.
3668 o Major features, client performance:
3669 - Weight directory requests by advertised bandwidth. Now we can
3670 let servers enable write limiting but still allow most clients to
3671 succeed at their directory requests. (We still ignore weights when
3672 choosing a directory authority; I hope this is a feature.)
3673 - Stop overloading exit nodes -- avoid choosing them for entry or
3674 middle hops when the total bandwidth available from non-exit nodes
3675 is much higher than the total bandwidth available from exit nodes.
3676 - Rather than waiting a fixed amount of time between retrying
3677 application connections, we wait only 10 seconds for the first,
3678 10 seconds for the second, and 15 seconds for each retry after
3679 that. Hopefully this will improve the expected user experience.
3680 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
3681 to open a stream fails; now we do in more cases. This should
3682 make clients able to find a good exit faster in some cases, since
3683 unhandleable requests will now get an error rather than timing out.
3685 o Major features, client functionality:
3686 - Implement BEGIN_DIR cells, so we can connect to a directory
3687 server via TLS to do encrypted directory requests rather than
3688 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
3689 config options if you like. For now, this feature only works if
3690 you already have a descriptor for the destination dirserver.
3691 - Add support for transparent application connections: this basically
3692 bundles the functionality of trans-proxy-tor into the Tor
3693 mainline. Now hosts with compliant pf/netfilter implementations
3694 can redirect TCP connections straight to Tor without diverting
3695 through SOCKS. (Based on patch from tup.)
3696 - Add support for using natd; this allows FreeBSDs earlier than
3697 5.1.2 to have ipfw send connections through Tor without using
3698 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
3700 o Major features, servers:
3701 - Setting up a dyndns name for your server is now optional: servers
3702 with no hostname or IP address will learn their IP address by
3703 asking the directory authorities. This code only kicks in when you
3704 would normally have exited with a "no address" error. Nothing's
3705 authenticated, so use with care.
3706 - Directory servers now spool server descriptors, v1 directories,
3707 and v2 networkstatus objects to buffers as needed rather than en
3708 masse. They also mmap the cached-routers files. These steps save
3710 - Stop requiring clients to have well-formed certificates, and stop
3711 checking nicknames in certificates. (Clients have certificates so
3712 that they can look like Tor servers, but in the future we might want
3713 to allow them to look like regular TLS clients instead. Nicknames
3714 in certificates serve no purpose other than making our protocol
3715 easier to recognize on the wire.) Implements proposal 106.
3717 o Improvements on DNS support:
3718 - Add "eventdns" asynchronous dns library originally based on code
3719 from Adam Langley. Now we can discard the old rickety dnsworker
3720 concept, and support a wider variety of DNS functions. Allows
3721 multithreaded builds on NetBSD and OpenBSD again.
3722 - Add server-side support for "reverse" DNS lookups (using PTR
3723 records so clients can determine the canonical hostname for a given
3724 IPv4 address). Only supported by servers using eventdns; servers
3725 now announce in their descriptors if they don't support eventdns.
3726 - Workaround for name servers (like Earthlink's) that hijack failing
3727 DNS requests and replace the no-such-server answer with a "helpful"
3728 redirect to an advertising-driven search portal. Also work around
3729 DNS hijackers who "helpfully" decline to hijack known-invalid
3730 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
3731 lets you turn it off.
3732 - Servers now check for the case when common DNS requests are going to
3733 wildcarded addresses (i.e. all getting the same answer), and change
3734 their exit policy to reject *:* if it's happening.
3735 - When asked to resolve a hostname, don't use non-exit servers unless
3736 requested to do so. This allows servers with broken DNS to be
3737 useful to the network.
3738 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
3739 useless IPv6 DNS resolves.
3740 - Specify and implement client-side SOCKS5 interface for reverse DNS
3741 lookups (see doc/socks-extensions.txt). Also cache them.
3742 - When we change nameservers or IP addresses, reset and re-launch
3743 our tests for DNS hijacking.
3745 o Improvements on reachability testing:
3746 - Servers send out a burst of long-range padding cells once they've
3747 established that they're reachable. Spread them over 4 circuits,
3748 so hopefully a few will be fast. This exercises bandwidth and
3749 bootstraps them into the directory more quickly.
3750 - When we find our DirPort to be reachable, publish a new descriptor
3751 so we'll tell the world (reported by pnx).
3752 - Directory authorities now only decide that routers are reachable
3753 if their identity keys are as expected.
3754 - Do DirPort reachability tests less often, since a single test
3755 chews through many circuits before giving up.
3756 - Avoid some false positives during reachability testing: don't try
3757 to test via a server that's on the same /24 network as us.
3758 - Start publishing one minute or so after we find our ORPort
3759 to be reachable. This will help reduce the number of descriptors
3760 we have for ourselves floating around, since it's quite likely
3761 other things (e.g. DirPort) will change during that minute too.
3762 - Routers no longer try to rebuild long-term connections to directory
3763 authorities, and directory authorities no longer try to rebuild
3764 long-term connections to all servers. We still don't hang up
3765 connections in these two cases though -- we need to look at it
3766 more carefully to avoid flapping, and we likely need to wait til
3767 0.1.1.x is obsolete.
3769 o Improvements on rate limiting:
3770 - Enable write limiting as well as read limiting. Now we sacrifice
3771 capacity if we're pushing out lots of directory traffic, rather
3772 than overrunning the user's intended bandwidth limits.
3773 - Include TLS overhead when counting bandwidth usage; previously, we
3774 would count only the bytes sent over TLS, but not the bytes used
3776 - Servers decline directory requests much more aggressively when
3777 they're low on bandwidth. Otherwise they end up queueing more and
3778 more directory responses, which can't be good for latency.
3779 - But never refuse directory requests from local addresses.
3780 - Be willing to read or write on local connections (e.g. controller
3781 connections) even when the global rate limiting buckets are empty.
3782 - Flush local controller connection buffers periodically as we're
3783 writing to them, so we avoid queueing 4+ megabytes of data before
3785 - Revise and clean up the torrc.sample that we ship with; add
3786 a section for BandwidthRate and BandwidthBurst.
3788 o Major features, NT services:
3789 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
3790 command-line flag so that admins can override the default by saying
3791 "tor --service install --user "SomeUser"". This will not affect
3792 existing installed services. Also, warn the user that the service
3793 will look for its configuration file in the service user's
3794 %appdata% directory. (We can't do the "hardwire the user's appdata
3795 directory" trick any more, since we may not have read access to that
3797 - Support running the Tor service with a torrc not in the same
3798 directory as tor.exe and default to using the torrc located in
3799 the %appdata%\Tor\ of the user who installed the service. Patch
3801 - Add an --ignore-missing-torrc command-line option so that we can
3802 get the "use sensible defaults if the configuration file doesn't
3803 exist" behavior even when specifying a torrc location on the
3805 - When stopping an NT service, wait up to 10 sec for it to actually
3806 stop. (Patch from Matt Edman; resolves bug 295.)
3808 o Directory authority improvements:
3809 - Stop letting hibernating or obsolete servers affect uptime and
3811 - Stop listing hibernating servers in the v1 directory.
3812 - Authorities no longer recommend exits as guards if this would shift
3813 too much load to the exit nodes.
3814 - Authorities now specify server versions in networkstatus. This adds
3815 about 2% to the size of compressed networkstatus docs, and allows
3816 clients to tell which servers support BEGIN_DIR and which don't.
3817 The implementation is forward-compatible with a proposed future
3818 protocol version scheme not tied to Tor versions.
3819 - DirServer configuration lines now have an orport= option so
3820 clients can open encrypted tunnels to the authorities without
3821 having downloaded their descriptors yet. Enabled for moria1,
3822 moria2, tor26, and lefkada now in the default configuration.
3823 - Add a BadDirectory flag to network status docs so that authorities
3824 can (eventually) tell clients about caches they believe to be
3825 broken. Not used yet.
3826 - Allow authorities to list nodes as bad exits in their
3827 approved-routers file by fingerprint or by address. If most
3828 authorities set a BadExit flag for a server, clients don't think
3829 of it as a general-purpose exit. Clients only consider authorities
3830 that advertise themselves as listing bad exits.
3831 - Patch from Steve Hildrey: Generate network status correctly on
3832 non-versioning dirservers.
3833 - Have directory authorities allow larger amounts of drift in uptime
3834 without replacing the server descriptor: previously, a server that
3835 restarted every 30 minutes could have 48 "interesting" descriptors
3837 - Reserve the nickname "Unnamed" for routers that can't pick
3838 a hostname: any router can call itself Unnamed; directory
3839 authorities will never allocate Unnamed to any particular router;
3840 clients won't believe that any router is the canonical Unnamed.
3842 o Directory mirrors and clients:
3843 - Discard any v1 directory info that's over 1 month old (for
3844 directories) or over 1 week old (for running-routers lists).
3845 - Clients track responses with status 503 from dirservers. After a
3846 dirserver has given us a 503, we try not to use it until an hour has
3847 gone by, or until we have no dirservers that haven't given us a 503.
3848 - When we get a 503 from a directory, and we're not a server, we no
3849 longer count the failure against the total number of failures
3850 allowed for the object we're trying to download.
3851 - Prepare for servers to publish descriptors less often: never
3852 discard a descriptor simply for being too old until either it is
3853 recommended by no authorities, or until we get a better one for
3854 the same router. Make caches consider retaining old recommended
3855 routers for even longer.
3856 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
3857 headers for content, so that we can work better in the presence of
3858 caching HTTP proxies.
3859 - Stop fetching descriptors if you're not a dir mirror and you
3860 haven't tried to establish any circuits lately. (This currently
3861 causes some dangerous behavior, because when you start up again
3862 you'll use your ancient server descriptors.)
3864 o Major fixes, crashes:
3865 - Stop crashing when the controller asks us to resetconf more than
3866 one config option at once. (Vidalia 0.0.11 does this.)
3867 - Fix a longstanding obscure crash bug that could occur when we run
3868 out of DNS worker processes, if we're not using eventdns. (Resolves
3870 - Fix an assert that could trigger if a controller quickly set then
3871 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
3872 - Avoid crash when telling controller about stream-status and a
3874 - Avoid sending junk to controllers or segfaulting when a controller
3875 uses EVENT_NEW_DESC with verbose nicknames.
3876 - Stop triggering asserts if the controller tries to extend hidden
3877 service circuits (reported by mwenge).
3878 - If we start a server with ClientOnly 1, then set ClientOnly to 0
3879 and hup, stop triggering an assert based on an empty onion_key.
3880 - Mask out all signals in sub-threads; only the libevent signal
3881 handler should be processing them. This should prevent some crashes
3882 on some machines using pthreads. (Patch from coderman.)
3883 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
3885 o Major fixes, anonymity/security:
3886 - Automatically avoid picking more than one node from the same
3887 /16 network when constructing a circuit. Add an
3888 "EnforceDistinctSubnets" option to let people disable it if they
3889 want to operate private test networks on a single subnet.
3890 - When generating bandwidth history, round down to the nearest
3891 1k. When storing accounting data, round up to the nearest 1k.
3892 - When we're running as a server, remember when we last rotated onion
3893 keys, so that we will rotate keys once they're a week old even if
3894 we never stay up for a week ourselves.
3895 - If a client asked for a server by name, and there's a named server
3896 in our network-status but we don't have its descriptor yet, we
3897 could return an unnamed server instead.
3898 - Reject (most) attempts to use Tor circuits with length one. (If
3899 many people start using Tor as a one-hop proxy, exit nodes become
3900 a more attractive target for compromise.)
3901 - Just because your DirPort is open doesn't mean people should be
3902 able to remotely teach you about hidden service descriptors. Now
3903 only accept rendezvous posts if you've got HSAuthoritativeDir set.
3904 - Fix a potential race condition in the rpm installer. Found by
3906 - Do not log IPs with TLS failures for incoming TLS
3907 connections. (Fixes bug 382.)
3909 o Major fixes, other:
3910 - If our system clock jumps back in time, don't publish a negative
3911 uptime in the descriptor.
3912 - When we start during an accounting interval before it's time to wake
3913 up, remember to wake up at the correct time. (May fix bug 342.)
3914 - Previously, we would cache up to 16 old networkstatus documents
3915 indefinitely, if they came from nontrusted authorities. Now we
3916 discard them if they are more than 10 days old.
3917 - When we have a state file we cannot parse, tell the user and
3918 move it aside. Now we avoid situations where the user starts
3919 Tor in 1904, Tor writes a state file with that timestamp in it,
3920 the user fixes her clock, and Tor refuses to start.
3921 - Publish a new descriptor after we hup/reload. This is important
3922 if our config has changed such that we'll want to start advertising
3923 our DirPort now, etc.
3924 - If we are using an exit enclave and we can't connect, e.g. because
3925 its webserver is misconfigured to not listen on localhost, then
3926 back off and try connecting from somewhere else before we fail.
3928 o New config options or behaviors:
3929 - When EntryNodes are configured, rebuild the guard list to contain,
3930 in order: the EntryNodes that were guards before; the rest of the
3931 EntryNodes; the nodes that were guards before.
3932 - Do not warn when individual nodes in the configuration's EntryNodes,
3933 ExitNodes, etc are down: warn only when all possible nodes
3934 are down. (Fixes bug 348.)
3935 - Put a lower-bound on MaxAdvertisedBandwidth.
3936 - Start using the state file to store bandwidth accounting data:
3937 the bw_accounting file is now obsolete. We'll keep generating it
3938 for a while for people who are still using 0.1.2.4-alpha.
3939 - Try to batch changes to the state file so that we do as few
3940 disk writes as possible while still storing important things in
3942 - The state file and the bw_accounting file get saved less often when
3943 the AvoidDiskWrites config option is set.
3944 - Make PIDFile work on Windows.
3945 - Add internal descriptions for a bunch of configuration options:
3946 accessible via controller interface and in comments in saved
3948 - Reject *:563 (NNTPS) in the default exit policy. We already reject
3949 NNTP by default, so this seems like a sensible addition.
3950 - Clients now reject hostnames with invalid characters. This should
3951 avoid some inadvertent info leaks. Add an option
3952 AllowNonRFC953Hostnames to disable this behavior, in case somebody
3953 is running a private network with hosts called @, !, and #.
3954 - Check for addresses with invalid characters at the exit as well,
3955 and warn less verbosely when they fail. You can override this by
3956 setting ServerDNSAllowNonRFC953Addresses to 1.
3957 - Remove some options that have been deprecated since at least
3958 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
3959 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
3960 to set log options. Mark PathlenCoinWeight as obsolete.
3961 - Stop accepting certain malformed ports in configured exit policies.
3962 - When the user uses bad syntax in the Log config line, stop
3963 suggesting other bad syntax as a replacement.
3964 - Add new config option "ResolvConf" to let the server operator
3965 choose an alternate resolve.conf file when using eventdns.
3966 - If one of our entry guards is on the ExcludeNodes list, or the
3967 directory authorities don't think it's a good guard, treat it as
3968 if it were unlisted: stop using it as a guard, and throw it off
3969 the guards list if it stays that way for a long time.
3970 - Allow directory authorities to be marked separately as authorities
3971 for the v1 directory protocol, the v2 directory protocol, and
3972 as hidden service directories, to make it easier to retire old
3973 authorities. V1 authorities should set "HSAuthoritativeDir 1"
3974 to continue being hidden service authorities too.
3975 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
3976 - Make TrackExitHosts case-insensitive, and fix the behavior of
3977 ".suffix" TrackExitHosts items to avoid matching in the middle of
3979 - New DirPort behavior: if you have your dirport set, you download
3980 descriptors aggressively like a directory mirror, whether or not
3984 - Create a new file ReleaseNotes which was the old ChangeLog. The
3985 new ChangeLog file now includes the notes for all development
3987 - Add a new address-spec.txt document to describe our special-case
3988 addresses: .exit, .onion, and .noconnnect.
3989 - Fork the v1 directory protocol into its own spec document,
3990 and mark dir-spec.txt as the currently correct (v2) spec.
3992 o Packaging, porting, and contrib
3993 - "tor --verify-config" now exits with -1(255) or 0 depending on
3994 whether the config options are bad or good.
3995 - The Debian package now uses --verify-config when (re)starting,
3996 to distinguish configuration errors from other errors.
3997 - Adapt a patch from goodell to let the contrib/exitlist script
3998 take arguments rather than require direct editing.
3999 - Prevent the contrib/exitlist script from printing the same
4000 result more than once.
4001 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
4002 - In the hidden service example in torrc.sample, stop recommending
4003 esoteric and discouraged hidden service options.
4004 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
4005 values before failing, and always enables eventdns.
4006 - Try to detect Windows correctly when cross-compiling.
4007 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
4008 Try to fix this in configure.in by checking for most functions
4009 before we check for libevent.
4010 - Update RPMs to require libevent 1.2.
4011 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
4012 or later. Log when we are doing this, so we can diagnose it when
4013 it fails. (Also, recommend libevent 1.1b for kqueue and
4014 win32 methods; deprecate libevent 1.0b harder; make libevent
4015 recommendation system saner.)
4016 - Build with recent (1.3+) libevents on platforms that do not
4017 define the nonstandard types "u_int8_t" and friends.
4018 - Remove architecture from OS X builds. The official builds are
4019 now universal binaries.
4020 - Run correctly on OS X platforms with case-sensitive filesystems.
4021 - Correctly set maximum connection limit on Cygwin. (This time
4023 - Start compiling on MinGW on Windows (patches from Mike Chiussi
4025 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
4026 - Finally fix the openssl warnings from newer gccs that believe that
4027 ignoring a return value is okay, but casting a return value and
4028 then ignoring it is a sign of madness.
4029 - On architectures where sizeof(int)>4, still clamp declarable
4030 bandwidth to INT32_MAX.
4032 o Minor features, controller:
4033 - Warn the user when an application uses the obsolete binary v0
4034 control protocol. We're planning to remove support for it during
4035 the next development series, so it's good to give people some
4037 - Add STREAM_BW events to report per-entry-stream bandwidth
4038 use. (Patch from Robert Hogan.)
4039 - Rate-limit SIGNEWNYM signals in response to controllers that
4040 impolitely generate them for every single stream. (Patch from
4041 mwenge; closes bug 394.)
4042 - Add a REMAP status to stream events to note that a stream's
4043 address has changed because of a cached address or a MapAddress
4045 - Make REMAP stream events have a SOURCE (cache or exit), and
4046 make them generated in every case where we get a successful
4047 connected or resolved cell.
4048 - Track reasons for OR connection failure; make these reasons
4049 available via the controller interface. (Patch from Mike Perry.)
4050 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
4051 can learn when clients are sending malformed hostnames to Tor.
4052 - Specify and implement some of the controller status events.
4053 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
4054 - Reimplement GETINFO so that info/names stays in sync with the
4056 - Implement "GETINFO fingerprint".
4057 - Implement "SETEVENTS GUARD" so controllers can get updates on
4058 entry guard status as it changes.
4059 - Make all connections to addresses of the form ".noconnect"
4060 immediately get closed. This lets application/controller combos
4061 successfully test whether they're talking to the same Tor by
4062 watching for STREAM events.
4063 - Add a REASON field to CIRC events; for backward compatibility, this
4064 field is sent only to controllers that have enabled the extended
4065 event format. Also, add additional reason codes to explain why
4066 a given circuit has been destroyed or truncated. (Patches from
4068 - Add a REMOTE_REASON field to extended CIRC events to tell the
4069 controller why a remote OR told us to close a circuit.
4070 - Stream events also now have REASON and REMOTE_REASON fields,
4071 working much like those for circuit events.
4072 - There's now a GETINFO ns/... field so that controllers can ask Tor
4073 about the current status of a router.
4074 - A new event type "NS" to inform a controller when our opinion of
4075 a router's status has changed.
4076 - Add a GETINFO events/names and GETINFO features/names so controllers
4077 can tell which events and features are supported.
4078 - A new CLEARDNSCACHE signal to allow controllers to clear the
4079 client-side DNS cache without expiring circuits.
4080 - Fix CIRC controller events so that controllers can learn the
4081 identity digests of non-Named servers used in circuit paths.
4082 - Let controllers ask for more useful identifiers for servers. Instead
4083 of learning identity digests for un-Named servers and nicknames
4084 for Named servers, the new identifiers include digest, nickname,
4085 and indication of Named status. Off by default; see control-spec.txt
4086 for more information.
4087 - Add a "getinfo address" controller command so it can display Tor's
4088 best guess to the user.
4089 - New controller event to alert the controller when our server
4090 descriptor has changed.
4091 - Give more meaningful errors on controller authentication failure.
4092 - Export the default exit policy via the control port, so controllers
4093 don't need to guess what it is / will be later.
4095 o Minor bugfixes, controller:
4096 - When creating a circuit via the controller, send a 'launched'
4097 event when we're done, so we follow the spec better.
4098 - Correct the control spec to match how the code actually responds
4099 to 'getinfo addr-mappings/*'. Reported by daejees.
4100 - The control spec described a GUARDS event, but the code
4101 implemented a GUARD event. Standardize on GUARD, but let people
4102 ask for GUARDS too. Reported by daejees.
4103 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
4104 clear the corresponding on_circuit variable, and remember later
4105 that we don't need to send a redundant CLOSED event. (Resolves part
4107 - Report events where a resolve succeeded or where we got a socks
4108 protocol error correctly, rather than calling both of them
4110 - Change reported stream target addresses to IP consistently when
4111 we finally get the IP from an exit node.
4112 - Send log messages to the controller even if they happen to be very
4114 - Flush ERR-level controller status events just like we currently
4115 flush ERR-level log events, so that a Tor shutdown doesn't prevent
4116 the controller from learning about current events.
4117 - Report the circuit number correctly in STREAM CLOSED events. Bug
4118 reported by Mike Perry.
4119 - Do not report bizarre values for results of accounting GETINFOs
4120 when the last second's write or read exceeds the allotted bandwidth.
4121 - Report "unrecognized key" rather than an empty string when the
4122 controller tries to fetch a networkstatus that doesn't exist.
4123 - When the controller does a "GETINFO network-status", tell it
4124 about even those routers whose descriptors are very old, and use
4125 long nicknames where appropriate.
4126 - Fix handling of verbose nicknames with ORCONN controller events:
4127 make them show up exactly when requested, rather than exactly when
4129 - Controller signals now work on non-Unix platforms that don't define
4130 SIGUSR1 and SIGUSR2 the way we expect.
4131 - Respond to SIGNAL command before we execute the signal, in case
4132 the signal shuts us down. Suggested by Karsten Loesing.
4133 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
4135 o Minor features, code performance:
4136 - Major performance improvement on inserting descriptors: change
4137 algorithm from O(n^2) to O(n).
4138 - Do not rotate onion key immediately after setting it for the first
4140 - Call router_have_min_dir_info half as often. (This is showing up in
4141 some profiles, but not others.)
4142 - When using GCC, make log_debug never get called at all, and its
4143 arguments never get evaluated, when no debug logs are configured.
4144 (This is showing up in some profiles, but not others.)
4145 - Statistics dumped by -USR2 now include a breakdown of public key
4146 operations, for profiling.
4147 - Make the common memory allocation path faster on machines where
4148 malloc(0) returns a pointer.
4149 - Split circuit_t into origin_circuit_t and or_circuit_t, and
4150 split connection_t into edge, or, dir, control, and base structs.
4151 These will save quite a bit of memory on busy servers, and they'll
4152 also help us track down bugs in the code and bugs in the spec.
4153 - Use OpenSSL's AES implementation on platforms where it's faster.
4154 This could save us as much as 10% CPU usage.
4156 o Minor features, descriptors and descriptor handling:
4157 - Avoid duplicate entries on MyFamily line in server descriptor.
4158 - When Tor receives a router descriptor that it asked for, but
4159 no longer wants (because it has received fresh networkstatuses
4160 in the meantime), do not warn the user. Cache the descriptor if
4161 we're a cache; drop it if we aren't.
4162 - Servers no longer ever list themselves in their "family" line,
4163 even if configured to do so. This makes it easier to configure
4164 family lists conveniently.
4166 o Minor fixes, confusing/misleading log messages:
4167 - Display correct results when reporting which versions are
4168 recommended, and how recommended they are. (Resolves bug 383.)
4169 - Inform the server operator when we decide not to advertise a
4170 DirPort due to AccountingMax enabled or a low BandwidthRate.
4171 - Only include function names in log messages for info/debug messages.
4172 For notice/warn/err, the content of the message should be clear on
4173 its own, and printing the function name only confuses users.
4174 - Remove even more protocol-related warnings from Tor server logs,
4175 such as bad TLS handshakes and malformed begin cells.
4176 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
4177 when the IP address is mapped through MapAddress to a hostname.
4178 - Fix misleading log messages: an entry guard that is "unlisted",
4179 as well as not known to be "down" (because we've never heard
4180 of it), is not therefore "up".
4182 o Minor fixes, old/obsolete behavior:
4183 - Start assuming we can use a create_fast cell if we don't know
4184 what version a router is running.
4185 - We no longer look for identity and onion keys in "identity.key" and
4186 "onion.key" -- these were replaced by secret_id_key and
4187 secret_onion_key in 0.0.8pre1.
4188 - We no longer require unrecognized directory entries to be
4190 - Drop compatibility with obsolete Tors that permit create cells
4191 to have the wrong circ_id_type.
4192 - Remove code to special-case "-cvs" ending, since it has not
4193 actually mattered since 0.0.9.
4194 - Don't re-write the fingerprint file every restart, unless it has
4197 o Minor fixes, misc client-side behavior:
4198 - Always remove expired routers and networkstatus docs before checking
4199 whether we have enough information to build circuits. (Fixes
4201 - When computing clock skew from directory HTTP headers, consider what
4202 time it was when we finished asking for the directory, not what
4204 - Make our socks5 handling more robust to broken socks clients:
4205 throw out everything waiting on the buffer in between socks
4206 handshake phases, since they can't possibly (so the theory
4207 goes) have predicted what we plan to respond to them.
4208 - Expire socks connections if they spend too long waiting for the
4209 handshake to finish. Previously we would let them sit around for
4210 days, if the connecting application didn't close them either.
4211 - And if the socks handshake hasn't started, don't send a
4212 "DNS resolve socks failed" handshake reply; just close it.
4213 - If the user asks to use invalid exit nodes, be willing to use
4215 - Track unreachable entry guards correctly: don't conflate
4216 'unreachable by us right now' with 'listed as down by the directory
4217 authorities'. With the old code, if a guard was unreachable by us
4218 but listed as running, it would clog our guard list forever.
4219 - Behave correctly in case we ever have a network with more than
4220 2GB/s total advertised capacity.
4221 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
4222 - Fix a memory leak when we ask for "all" networkstatuses and we
4223 get one we don't recognize.
4226 Changes in version 0.1.1.26 - 2006-12-14
4227 o Security bugfixes:
4228 - Stop sending the HttpProxyAuthenticator string to directory
4229 servers when directory connections are tunnelled through Tor.
4230 - Clients no longer store bandwidth history in the state file.
4231 - Do not log introduction points for hidden services if SafeLogging
4235 - Fix an assert failure when a directory authority sets
4236 AuthDirRejectUnlisted and then receives a descriptor from an
4237 unlisted router (reported by seeess).
4240 Changes in version 0.1.1.25 - 2006-11-04
4242 - When a client asks us to resolve (rather than connect to)
4243 an address, and we have a cached answer, give them the cached
4244 answer. Previously, we would give them no answer at all.
4245 - We were building exactly the wrong circuits when we predict
4246 hidden service requirements, meaning Tor would have to build all
4247 its circuits on demand.
4248 - If none of our live entry guards have a high uptime, but we
4249 require a guard with a high uptime, try adding a new guard before
4250 we give up on the requirement. This patch should make long-lived
4251 connections more stable on average.
4252 - When testing reachability of our DirPort, don't launch new
4253 tests when there's already one in progress -- unreachable
4254 servers were stacking up dozens of testing streams.
4256 o Security bugfixes:
4257 - When the user sends a NEWNYM signal, clear the client-side DNS
4258 cache too. Otherwise we continue to act on previous information.
4261 - Avoid a memory corruption bug when creating a hash table for
4263 - Avoid possibility of controller-triggered crash when misusing
4264 certain commands from a v0 controller on platforms that do not
4265 handle printf("%s",NULL) gracefully.
4266 - Avoid infinite loop on unexpected controller input.
4267 - Don't log spurious warnings when we see a circuit close reason we
4268 don't recognize; it's probably just from a newer version of Tor.
4269 - Add Vidalia to the OS X uninstaller script, so when we uninstall
4270 Tor/Privoxy we also uninstall Vidalia.
4273 Changes in version 0.1.1.24 - 2006-09-29
4275 - Allow really slow clients to not hang up five minutes into their
4276 directory downloads (suggested by Adam J. Richter).
4277 - Fix major performance regression from 0.1.0.x: instead of checking
4278 whether we have enough directory information every time we want to
4279 do something, only check when the directory information has changed.
4280 This should improve client CPU usage by 25-50%.
4281 - Don't crash if, after a server has been running for a while,
4282 it can't resolve its hostname.
4283 - When a client asks us to resolve (not connect to) an address,
4284 and we have a cached answer, give them the cached answer.
4285 Previously, we would give them no answer at all.
4288 - Allow Tor to start when RunAsDaemon is set but no logs are set.
4289 - Don't crash when the controller receives a third argument to an
4290 "extendcircuit" request.
4291 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
4292 response; fix error code when "getinfo dir/status/" fails.
4293 - Fix configure.in to not produce broken configure files with
4294 more recent versions of autoconf. Thanks to Clint for his auto*
4296 - Fix security bug on NetBSD that could allow someone to force
4297 uninitialized RAM to be sent to a server's DNS resolver. This
4298 only affects NetBSD and other platforms that do not bounds-check
4300 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
4301 methods: these are known to be buggy.
4302 - If we're a directory mirror and we ask for "all" network status
4303 documents, we would discard status documents from authorities
4307 Changes in version 0.1.1.23 - 2006-07-30
4309 - Fast Tor servers, especially exit nodes, were triggering asserts
4310 due to a bug in handling the list of pending DNS resolves. Some
4311 bugs still remain here; we're hunting them.
4312 - Entry guards could crash clients by sending unexpected input.
4313 - More fixes on reachability testing: if you find yourself reachable,
4314 then don't ever make any client requests (so you stop predicting
4315 circuits), then hup or have your clock jump, then later your IP
4316 changes, you won't think circuits are working, so you won't try to
4317 test reachability, so you won't publish.
4320 - Avoid a crash if the controller does a resetconf firewallports
4321 and then a setconf fascistfirewall=1.
4322 - Avoid an integer underflow when the dir authority decides whether
4323 a router is stable: we might wrongly label it stable, and compute
4324 a slightly wrong median stability, when a descriptor is published
4326 - Fix a place where we might trigger an assert if we can't build our
4327 own server descriptor yet.
4330 Changes in version 0.1.1.22 - 2006-07-05
4332 - Fix a big bug that was causing servers to not find themselves
4333 reachable if they changed IP addresses. Since only 0.1.1.22+
4334 servers can do reachability testing correctly, now we automatically
4335 make sure to test via one of these.
4336 - Fix to allow clients and mirrors to learn directory info from
4337 descriptor downloads that get cut off partway through.
4338 - Directory authorities had a bug in deciding if a newly published
4339 descriptor was novel enough to make everybody want a copy -- a few
4340 servers seem to be publishing new descriptors many times a minute.
4342 - Fix a rare bug that was causing some servers to complain about
4343 "closing wedged cpuworkers" and skip some circuit create requests.
4344 - Make the Exit flag in directory status documents actually work.
4347 Changes in version 0.1.1.21 - 2006-06-10
4348 o Crash and assert fixes from 0.1.1.20:
4349 - Fix a rare crash on Tor servers that have enabled hibernation.
4350 - Fix a seg fault on startup for Tor networks that use only one
4351 directory authority.
4352 - Fix an assert from a race condition that occurs on Tor servers
4353 while exiting, where various threads are trying to log that they're
4354 exiting, and delete the logs, at the same time.
4355 - Make our unit tests pass again on certain obscure platforms.
4358 - Add support for building SUSE RPM packages.
4359 - Speed up initial bootstrapping for clients: if we are making our
4360 first ever connection to any entry guard, then don't mark it down
4362 - When only one Tor server in the network is labelled as a guard,
4363 and we've already picked him, we would cycle endlessly picking him
4364 again, being unhappy about it, etc. Now we specifically exclude
4365 current guards when picking a new guard.
4366 - Servers send create cells more reliably after the TLS connection
4367 is established: we were sometimes forgetting to send half of them
4368 when we had more than one pending.
4369 - If we get a create cell that asks us to extend somewhere, but the
4370 Tor server there doesn't match the expected digest, we now send
4371 a destroy cell back, rather than silently doing nothing.
4372 - Make options->RedirectExit work again.
4373 - Make cookie authentication for the controller work again.
4374 - Stop being picky about unusual characters in the arguments to
4375 mapaddress. It's none of our business.
4376 - Add a new config option "TestVia" that lets you specify preferred
4377 middle hops to use for test circuits. Perhaps this will let me
4378 debug the reachability problems better.
4380 o Log / documentation fixes:
4381 - If we're a server and some peer has a broken TLS certificate, don't
4382 log about it unless ProtocolWarnings is set, i.e., we want to hear
4383 about protocol violations by others.
4384 - Fix spelling of VirtualAddrNetwork in man page.
4385 - Add a better explanation at the top of the autogenerated torrc file
4386 about what happened to our old torrc.
4389 Changes in version 0.1.1.20 - 2006-05-23
4390 o Crash and assert fixes from 0.1.0.17:
4391 - Fix assert bug in close_logs() on exit: when we close and delete
4392 logs, remove them all from the global "logfiles" list.
4393 - Fix an assert error when we're out of space in the connection_list
4394 and we try to post a hidden service descriptor (reported by Peter
4396 - Fix a rare assert error when we've tried all intro points for
4397 a hidden service and we try fetching the service descriptor again:
4398 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed".
4399 - Setconf SocksListenAddress kills Tor if it fails to bind. Now back
4400 out and refuse the setconf if it would fail.
4401 - If you specify a relative torrc path and you set RunAsDaemon in
4402 your torrc, then it chdir()'s to the new directory. If you then
4403 HUP, it tries to load the new torrc location, fails, and exits.
4404 The fix: no longer allow a relative path to torrc when using -f.
4405 - Check for integer overflows in more places, when adding elements
4406 to smartlists. This could possibly prevent a buffer overflow
4407 on malicious huge inputs.
4409 o Security fixes, major:
4410 - When we're printing strings from the network, don't try to print
4411 non-printable characters. Now we're safer against shell escape
4412 sequence exploits, and also against attacks to fool users into
4413 misreading their logs.
4414 - Implement entry guards: automatically choose a handful of entry
4415 nodes and stick with them for all circuits. Only pick new guards
4416 when the ones you have are unsuitable, and if the old guards
4417 become suitable again, switch back. This will increase security
4418 dramatically against certain end-point attacks. The EntryNodes
4419 config option now provides some hints about which entry guards you
4420 want to use most; and StrictEntryNodes means to only use those.
4421 Fixes CVE-2006-0414.
4422 - Implement exit enclaves: if we know an IP address for the
4423 destination, and there's a running Tor server at that address
4424 which allows exit to the destination, then extend the circuit to
4425 that exit first. This provides end-to-end encryption and end-to-end
4426 authentication. Also, if the user wants a .exit address or enclave,
4427 use 4 hops rather than 3, and cannibalize a general circ for it
4429 - Obey our firewall options more faithfully:
4430 . If we can't get to a dirserver directly, try going via Tor.
4431 . Don't ever try to connect (as a client) to a place our
4432 firewall options forbid.
4433 . If we specify a proxy and also firewall options, obey the
4434 firewall options even when we're using the proxy: some proxies
4435 can only proxy to certain destinations.
4436 - Make clients regenerate their keys when their IP address changes.
4437 - For the OS X package's modified privoxy config file, comment
4438 out the "logfile" line so we don't log everything passed
4440 - Our TLS handshakes were generating a single public/private
4441 keypair for the TLS context, rather than making a new one for
4442 each new connection. Oops. (But we were still rotating them
4443 periodically, so it's not so bad.)
4444 - When we were cannibalizing a circuit with a particular exit
4445 node in mind, we weren't checking to see if that exit node was
4446 already present earlier in the circuit. Now we are.
4447 - Require server descriptors to list IPv4 addresses -- hostnames
4448 are no longer allowed. This also fixes potential vulnerabilities
4449 to servers providing hostnames as their address and then
4450 preferentially resolving them so they can partition users.
4451 - Our logic to decide if the OR we connected to was the right guy
4452 was brittle and maybe open to a mitm for invalid routers.
4454 o Security fixes, minor:
4455 - Adjust tor-spec.txt to parameterize cell and key lengths. Now
4456 Ian Goldberg can prove things about our handshake protocol more
4458 - Make directory authorities generate a separate "guard" flag to
4459 mean "would make a good entry guard". Clients now honor the
4460 is_guard flag rather than looking at is_fast or is_stable.
4461 - Try to list MyFamily elements by key, not by nickname, and warn
4462 if we've not heard of a server.
4463 - Start using RAND_bytes rather than RAND_pseudo_bytes from
4464 OpenSSL. Also, reseed our entropy every hour, not just at
4465 startup. And add entropy in 512-bit chunks, not 160-bit chunks.
4466 - Refuse server descriptors where the fingerprint line doesn't match
4467 the included identity key. Tor doesn't care, but other apps (and
4468 humans) might actually be trusting the fingerprint line.
4469 - We used to kill the circuit when we receive a relay command we
4470 don't recognize. Now we just drop that cell.
4471 - Fix a bug found by Lasse Overlier: when we were making internal
4472 circuits (intended to be cannibalized later for rendezvous and
4473 introduction circuits), we were picking them so that they had
4474 useful exit nodes. There was no need for this, and it actually
4475 aids some statistical attacks.
4476 - Start treating internal circuits and exit circuits separately.
4477 It's important to keep them separate because internal circuits
4478 have their last hops picked like middle hops, rather than like
4479 exit hops. So exiting on them will break the user's expectations.
4480 - Fix a possible way to DoS dirservers.
4481 - When the client asked for a rendezvous port that the hidden
4482 service didn't want to provide, we were sending an IP address
4483 back along with the end cell. Fortunately, it was zero. But stop
4486 o Packaging improvements:
4487 - Implement --with-libevent-dir option to ./configure. Improve
4488 search techniques to find libevent, and use those for openssl too.
4489 - Fix a couple of bugs in OpenSSL detection. Deal better when
4490 there are multiple SSLs installed with different versions.
4491 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
4492 - On non-gcc compilers (e.g. Solaris's cc), use "-g -O" instead of
4494 - Make unit tests (and other invocations that aren't the real Tor)
4495 run without launching listeners, creating subdirectories, and so on.
4496 - The OS X installer was adding a symlink for tor_resolve but
4497 the binary was called tor-resolve (reported by Thomas Hardly).
4498 - Now we can target arch and OS in rpm builds (contributed by
4499 Phobos). Also make the resulting dist-rpm filename match the
4501 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
4502 if you log to syslog and want something other than LOG_DAEMON.
4503 - Fix the torify (tsocks) config file to not use Tor for localhost
4505 - Start shipping socks-extensions.txt, tor-doc-unix.html,
4506 tor-doc-server.html, and stylesheet.css in the tarball.
4507 - Stop shipping tor-doc.html, INSTALL, and README in the tarball.
4508 They are useless now.
4509 - Add Peter Palfrader's contributed check-tor script. It lets you
4510 easily check whether a given server (referenced by nickname)
4511 is reachable by you.
4512 - Add BSD-style contributed startup script "rc.subr" from Peter
4515 o Directory improvements -- new directory protocol:
4516 - See tor/doc/dir-spec.txt for all the juicy details. Key points:
4517 - Authorities and caches publish individual descriptors (by
4518 digest, by fingerprint, by "all", and by "tell me yours").
4519 - Clients don't download or use the old directory anymore. Now they
4520 download network-statuses from the directory authorities, and
4521 fetch individual server descriptors as needed from mirrors.
4522 - Clients don't download descriptors of non-running servers.
4523 - Download descriptors by digest, not by fingerprint. Caches try to
4524 download all listed digests from authorities; clients try to
4525 download "best" digests from caches. This avoids partitioning
4526 and isolating attacks better.
4527 - Only upload a new server descriptor when options change, 18
4528 hours have passed, uptime is reset, or bandwidth changes a lot.
4529 - Directory authorities silently throw away new descriptors that
4530 haven't changed much if the timestamps are similar. We do this to
4531 tolerate older Tor servers that upload a new descriptor every 15
4532 minutes. (It seemed like a good idea at the time.)
4533 - Clients choose directory servers from the network status lists,
4534 not from their internal list of router descriptors. Now they can
4535 go to caches directly rather than needing to go to authorities
4536 to bootstrap the first set of descriptors.
4537 - When picking a random directory, prefer non-authorities if any
4539 - Add a new flag to network-status indicating whether the server
4540 can answer v2 directory requests too.
4541 - Directory mirrors now cache up to 16 unrecognized network-status
4542 docs, so new directory authorities will be cached too.
4543 - Stop parsing, storing, or using running-routers output (but
4544 mirrors still cache and serve it).
4545 - Clients consider a threshold of "versioning" directory authorities
4546 before deciding whether to warn the user that he's obsolete.
4547 - Authorities publish separate sorted lists of recommended versions
4548 for clients and for servers.
4549 - Change DirServers config line to note which dirs are v1 authorities.
4550 - Put nicknames on the DirServer line, so we can refer to them
4551 without requiring all our users to memorize their IP addresses.
4552 - Remove option when getting directory cache to see whether they
4553 support running-routers; they all do now. Replace it with one
4554 to see whether caches support v2 stuff.
4555 - Stop listing down or invalid nodes in the v1 directory. This
4556 reduces its bulk by about 1/3, and reduces load on mirrors.
4557 - Mirrors no longer cache the v1 directory as often.
4558 - If we as a directory mirror don't know of any v1 directory
4559 authorities, then don't try to cache any v1 directories.
4561 o Other directory improvements:
4562 - Add lefkada.eecs.harvard.edu and tor.dizum.com as fourth and
4563 fifth authoritative directory servers.
4564 - Directory authorities no longer require an open connection from
4565 a server to consider him "reachable". We need this change because
4566 when we add new directory authorities, old servers won't know not
4568 - Dir authorities now do their own external reachability testing
4569 of each server, and only list as running the ones they found to
4570 be reachable. We also send back warnings to the server's logs if
4571 it uploads a descriptor that we already believe is unreachable.
4572 - Spread the directory authorities' reachability testing over the
4573 entire testing interval, so we don't try to do 500 TLS's at once
4575 - Make the "stable" router flag in network-status be the median of
4576 the uptimes of running valid servers, and make clients pay
4577 attention to the network-status flags. Thus the cutoff adapts
4578 to the stability of the network as a whole, making IRC, IM, etc
4579 connections more reliable.
4580 - Make the v2 dir's "Fast" flag based on relative capacity, just
4581 like "Stable" is based on median uptime. Name everything in the
4582 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
4583 - Retry directory requests if we fail to get an answer we like
4584 from a given dirserver (we were retrying before, but only if
4585 we fail to connect).
4586 - Return a robots.txt on our dirport to discourage google indexing.
4588 o Controller protocol improvements:
4589 - Revised controller protocol (version 1) that uses ascii rather
4590 than binary: tor/doc/control-spec.txt. Add supporting libraries
4591 in python and java and c# so you can use the controller from your
4592 applications without caring how our protocol works.
4593 - Allow the DEBUG controller event to work again. Mark certain log
4594 entries as "don't tell this to controllers", so we avoid cycles.
4595 - New controller function "getinfo accounting", to ask how
4596 many bytes we've used in this time period.
4597 - Add a "resetconf" command so you can set config options like
4598 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
4599 a config option in the torrc with no value, then it clears it
4600 entirely (rather than setting it to its default).
4601 - Add a "getinfo config-file" to tell us where torrc is. Also
4602 expose guard nodes, config options/names.
4603 - Add a "quit" command (when when using the controller manually).
4604 - Add a new signal "newnym" to "change pseudonyms" -- that is, to
4605 stop using any currently-dirty circuits for new streams, so we
4606 don't link new actions to old actions. This also occurs on HUP
4608 - If we would close a stream early (e.g. it asks for a .exit that
4609 we know would refuse it) but the LeaveStreamsUnattached config
4610 option is set by the controller, then don't close it.
4611 - Add a new controller event type "authdir_newdescs" that allows
4612 controllers to get all server descriptors that were uploaded to
4613 a router in its role as directory authority.
4614 - New controller option "getinfo desc/all-recent" to fetch the
4615 latest server descriptor for every router that Tor knows about.
4616 - Fix the controller's "attachstream 0" command to treat conn like
4617 it just connected, doing address remapping, handling .exit and
4618 .onion idioms, and so on. Now we're more uniform in making sure
4619 that the controller hears about new and closing connections.
4620 - Permit transitioning from ORPort==0 to ORPort!=0, and back, from
4621 the controller. Also, rotate dns and cpu workers if the controller
4622 changes options that will affect them; and initialize the dns
4623 worker cache tree whether or not we start out as a server.
4624 - Add a new circuit purpose 'controller' to let the controller ask
4625 for a circuit that Tor won't try to use. Extend the "extendcircuit"
4626 controller command to let you specify the purpose if you're starting
4627 a new circuit. Add a new "setcircuitpurpose" controller command to
4628 let you change a circuit's purpose after it's been created.
4629 - Let the controller ask for "getinfo dir/server/foo" so it can ask
4630 directly rather than connecting to the dir port. "getinfo
4631 dir/status/foo" also works, but currently only if your DirPort
4633 - Let the controller tell us about certain router descriptors
4634 that it doesn't want Tor to use in circuits. Implement
4635 "setrouterpurpose" and modify "+postdescriptor" to do this.
4636 - If the controller's *setconf commands fail, collect an error
4637 message in a string and hand it back to the controller -- don't
4638 just tell them to go read their logs.
4640 o Scalability, resource management, and performance:
4641 - Fix a major load balance bug: we were round-robin reading in 16 KB
4642 chunks, and servers with bandwidthrate of 20 KB, while downloading
4643 a 600 KB directory, would starve their other connections. Now we
4644 try to be a bit more fair.
4645 - Be more conservative about whether to advertise our DirPort.
4646 The main change is to not advertise if we're running at capacity
4647 and either a) we could hibernate ever or b) our capacity is low
4648 and we're using a default DirPort.
4649 - We weren't cannibalizing circuits correctly for
4650 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
4651 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
4652 build those from scratch. This should make hidden services faster.
4653 - Predict required circuits better, with an eye toward making hidden
4654 services faster on the service end.
4655 - Compress exit policies even more: look for duplicate lines and
4657 - Generate 18.0.0.0/8 address policy format in descs when we can;
4658 warn when the mask is not reducible to a bit-prefix.
4659 - There used to be two ways to specify your listening ports in a
4660 server descriptor: on the "router" line and with a separate "ports"
4661 line. Remove support for the "ports" line.
4662 - Reduce memory requirements in our structs by changing the order
4663 of fields. Replace balanced trees with hash tables. Inline
4664 bottleneck smartlist functions. Add a "Map from digest to void*"
4665 abstraction so we can do less hex encoding/decoding, and use it
4666 in router_get_by_digest(). Many other CPU and memory improvements.
4667 - Allow tor_gzip_uncompress to extract as much as possible from
4668 truncated compressed data. Try to extract as many
4669 descriptors as possible from truncated http responses (when
4670 purpose is DIR_PURPOSE_FETCH_ROUTERDESC).
4671 - Make circ->onionskin a pointer, not a static array. moria2 was using
4672 125000 circuit_t's after it had been up for a few weeks, which
4673 translates to 20+ megs of wasted space.
4674 - The private half of our EDH handshake keys are now chosen out
4675 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
4676 - Stop doing the complex voodoo overkill checking for insecure
4677 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
4678 - Do round-robin writes for TLS of at most 16 kB per write. This
4679 might be more fair on loaded Tor servers.
4680 - Do not use unaligned memory access on alpha, mips, or mipsel.
4681 It *works*, but is very slow, so we treat them as if it doesn't.
4683 o Other bugfixes and improvements:
4684 - Start storing useful information to $DATADIR/state, so we can
4685 remember things across invocations of Tor. Retain unrecognized
4686 lines so we can be forward-compatible, and write a TorVersion line
4687 so we can be backward-compatible.
4688 - If ORPort is set, Address is not explicitly set, and our hostname
4689 resolves to a private IP address, try to use an interface address
4690 if it has a public address. Now Windows machines that think of
4691 themselves as localhost can guess their address.
4692 - Regenerate our local descriptor if it's dirty and we try to use
4693 it locally (e.g. if it changes during reachability detection).
4694 This was causing some Tor servers to keep publishing the same
4695 initial descriptor forever.
4696 - Tor servers with dynamic IP addresses were needing to wait 18
4697 hours before they could start doing reachability testing using
4698 the new IP address and ports. This is because they were using
4699 the internal descriptor to learn what to test, yet they were only
4700 rebuilding the descriptor once they decided they were reachable.
4701 - It turns out we couldn't bootstrap a network since we added
4702 reachability detection in 0.1.0.1-rc. Good thing the Tor network
4703 has never gone down. Add an AssumeReachable config option to let
4704 servers and authorities bootstrap. When we're trying to build a
4705 high-uptime or high-bandwidth circuit but there aren't enough
4706 suitable servers, try being less picky rather than simply failing.
4707 - Newly bootstrapped Tor networks couldn't establish hidden service
4708 circuits until they had nodes with high uptime. Be more tolerant.
4709 - Really busy servers were keeping enough circuits open on stable
4710 connections that they were wrapping around the circuit_id
4711 space. (It's only two bytes.) This exposed a bug where we would
4712 feel free to reuse a circuit_id even if it still exists but has
4713 been marked for close. Try to fix this bug. Some bug remains.
4714 - When we fail to bind or listen on an incoming or outgoing
4715 socket, we now close it before refusing, rather than just
4716 leaking it. (Thanks to Peter Palfrader for finding.)
4717 - Fix a file descriptor leak in start_daemon().
4718 - On Windows, you can't always reopen a port right after you've
4719 closed it. So change retry_listeners() to only close and re-open
4720 ports that have changed.
4721 - Workaround a problem with some http proxies that refuse GET
4722 requests that specify "Content-Length: 0". Reported by Adrian.
4723 - Recover better from TCP connections to Tor servers that are
4724 broken but don't tell you (it happens!); and rotate TLS
4725 connections once a week.
4726 - Fix a scary-looking but apparently harmless bug where circuits
4727 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
4728 servers, and never switch to state CIRCUIT_STATE_OPEN.
4729 - Check for even more Windows version flags when writing the platform
4730 string in server descriptors, and note any we don't recognize.
4731 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
4732 get a better idea of why their circuits failed. Not used yet.
4733 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
4734 We don't use them yet, but maybe one day our DNS resolver will be
4735 able to discover them.
4736 - Let people type "tor --install" as well as "tor -install" when they
4737 want to make it an NT service.
4738 - Looks like we were never delivering deflated (i.e. compressed)
4739 running-routers lists, even when asked. Oops.
4740 - We were leaking some memory every time the client changed IPs.
4741 - Clean up more of the OpenSSL memory when exiting, so we can detect
4742 memory leaks better.
4743 - Never call free() on tor_malloc()d memory. This will help us
4744 use dmalloc to detect memory leaks.
4745 - Some Tor servers process billions of cells per day. These
4746 statistics are now uint64_t's.
4747 - Check [X-]Forwarded-For headers in HTTP requests when generating
4748 log messages. This lets people run dirservers (and caches) behind
4749 Apache but still know which IP addresses are causing warnings.
4750 - Fix minor integer overflow in calculating when we expect to use up
4751 our bandwidth allocation before hibernating.
4752 - Lower the minimum required number of file descriptors to 1000,
4753 so we can have some overhead for Valgrind on Linux, where the
4754 default ulimit -n is 1024.
4755 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
4756 and its existence is confusing some users.
4758 o Config option fixes:
4759 - Add a new config option ExitPolicyRejectPrivate which defaults
4760 to on. Now all exit policies will begin with rejecting private
4761 addresses, unless the server operator explicitly turns it off.
4762 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB.
4763 - Add new ReachableORAddresses and ReachableDirAddresses options
4764 that understand address policies. FascistFirewall is now a synonym
4765 for "ReachableORAddresses *:443", "ReachableDirAddresses *:80".
4766 - Start calling it FooListenAddress rather than FooBindAddress,
4767 since few of our users know what it means to bind an address
4769 - If the user gave Tor an odd number of command-line arguments,
4770 we were silently ignoring the last one. Now we complain and fail.
4771 This wins the oldest-bug prize -- this bug has been present since
4772 November 2002, as released in Tor 0.0.0.
4773 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
4774 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
4775 it would silently ignore the 6668.
4776 - If we get a linelist or linelist_s config option from the torrc,
4777 e.g. ExitPolicy, and it has no value, warn and skip rather than
4778 silently resetting it to its default.
4779 - Setconf was appending items to linelists, not clearing them.
4780 - Add MyFamily to torrc.sample in the server section, so operators
4781 will be more likely to learn that it exists.
4782 - Make ContactInfo mandatory for authoritative directory servers.
4783 - MaxConn has been obsolete for a while now. Document the ConnLimit
4784 config option, which is a *minimum* number of file descriptors
4785 that must be available else Tor refuses to start.
4786 - Get rid of IgnoreVersion undocumented config option, and make us
4787 only warn, never exit, when we're running an obsolete version.
4788 - Make MonthlyAccountingStart config option truly obsolete now.
4789 - Correct the man page entry on TrackHostExitsExpire.
4790 - Let directory authorities start even if they don't specify an
4791 Address config option.
4792 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
4793 reflect the updated flags in our v2 dir protocol.
4795 o Config option features:
4796 - Add a new config option FastFirstHopPK (on by default) so clients
4797 do a trivial crypto handshake for their first hop, since TLS has
4798 already taken care of confidentiality and authentication.
4799 - Let the user set ControlListenAddress in the torrc. This can be
4800 dangerous, but there are some cases (like a secured LAN) where it
4802 - New config options to help controllers: FetchServerDescriptors
4803 and FetchHidServDescriptors for whether to fetch server
4804 info and hidserv info or let the controller do it, and
4805 PublishServerDescriptor and PublishHidServDescriptors.
4806 - Also let the controller set the __AllDirActionsPrivate config
4807 option if you want all directory fetches/publishes to happen via
4808 Tor (it assumes your controller bootstraps your circuits).
4809 - Add "HardwareAccel" config option: support for crypto hardware
4810 accelerators via OpenSSL. Off by default, until we find somebody
4811 smart who can test it for us. (It appears to produce seg faults
4812 in at least some cases.)
4813 - New config option "AuthDirRejectUnlisted" for directory authorities
4814 as a panic button: if we get flooded with unusable servers we can
4815 revert to only listing servers in the approved-routers file.
4816 - Directory authorities can now reject/invalidate by key and IP,
4817 with the config options "AuthDirInvalid" and "AuthDirReject", or
4818 by marking a fingerprint as "!reject" or "!invalid" (as its
4819 nickname) in the approved-routers file. This is useful since
4820 currently we automatically list servers as running and usable
4821 even if we know they're jerks.
4822 - Add a new config option TestSocks so people can see whether their
4823 applications are using socks4, socks4a, socks5-with-ip, or
4824 socks5-with-fqdn. This way they don't have to keep mucking
4825 with tcpdump and wondering if something got cached somewhere.
4826 - Add "private:*" as an alias in configuration for policies. Now
4827 you can simplify your exit policy rather than needing to list
4828 every single internal or nonroutable network space.
4829 - Accept "private:*" in routerdesc exit policies; not generated yet
4830 because older Tors do not understand it.
4831 - Add configuration option "V1AuthoritativeDirectory 1" which
4832 moria1, moria2, and tor26 have set.
4833 - Implement an option, VirtualAddrMask, to set which addresses
4834 get handed out in response to mapaddress requests. This works
4835 around a bug in tsocks where 127.0.0.0/8 is never socksified.
4836 - Add a new config option FetchUselessDescriptors, off by default,
4837 for when you plan to run "exitlist" on your client and you want
4838 to know about even the non-running descriptors.
4839 - SocksTimeout: How long do we let a socks connection wait
4840 unattached before we fail it?
4841 - CircuitBuildTimeout: Cull non-open circuits that were born
4842 at least this many seconds ago.
4843 - CircuitIdleTimeout: Cull open clean circuits that were born
4844 at least this many seconds ago.
4845 - New config option SafeSocks to reject all application connections
4846 using unsafe socks protocols. Defaults to off.
4848 o Improved and clearer log messages:
4849 - Reduce clutter in server logs. We're going to try to make
4850 them actually usable now. New config option ProtocolWarnings that
4851 lets you hear about how _other Tors_ are breaking the protocol. Off
4853 - Divide log messages into logging domains. Once we put some sort
4854 of interface on this, it will let people looking at more verbose
4855 log levels specify the topics they want to hear more about.
4856 - Log server fingerprint on startup, so new server operators don't
4857 have to go hunting around their filesystem for it.
4858 - Provide dire warnings to any users who set DirServer manually;
4859 move it out of torrc.sample and into torrc.complete.
4860 - Make the log message less scary when all the dirservers are
4861 temporarily unreachable.
4862 - When tor_socketpair() fails in Windows, give a reasonable
4863 Windows-style errno back.
4864 - Improve tor_gettimeofday() granularity on windows.
4865 - We were printing the number of idle dns workers incorrectly when
4867 - Handle duplicate lines in approved-routers files without warning.
4868 - We were whining about using socks4 or socks5-with-local-lookup
4869 even when it's an IP address in the "virtual" range we designed
4870 exactly for this case.
4871 - Check for named servers when looking them up by nickname;
4872 warn when we're calling a non-named server by its nickname;
4873 don't warn twice about the same name.
4874 - Downgrade the dirserver log messages when whining about
4876 - Correct "your server is reachable" log entries to indicate that
4877 it was self-testing that told us so.
4878 - If we're trying to be a Tor server and running Windows 95/98/ME
4879 as a server, explain that we'll likely crash.
4880 - Provide a more useful warn message when our onion queue gets full:
4881 the CPU is too slow or the exit policy is too liberal.
4882 - Don't warn when we receive a 503 from a dirserver/cache -- this
4883 will pave the way for them being able to refuse if they're busy.
4884 - When we fail to bind a listener, try to provide a more useful
4885 log message: e.g., "Is Tor already running?"
4886 - Only start testing reachability once we've established a
4887 circuit. This will make startup on dir authorities less noisy.
4888 - Don't try to upload hidden service descriptors until we have
4889 established a circuit.
4890 - Tor didn't warn when it failed to open a log file.
4891 - Warn when listening on a public address for socks. We suspect a
4892 lot of people are setting themselves up as open socks proxies,
4893 and they have no idea that jerks on the Internet are using them,
4894 since they simply proxy the traffic into the Tor network.
4895 - Give a useful message when people run Tor as the wrong user,
4896 rather than telling them to start chowning random directories.
4897 - Fix a harmless bug that was causing Tor servers to log
4898 "Got an end because of misc error, but we're not an AP. Closing."
4899 - Fix wrong log message when you add a "HiddenServiceNodes" config
4900 line without any HiddenServiceDir line (reported by Chris Thomas).
4901 - Directory authorities now stop whining so loudly about bad
4902 descriptors that they fetch from other dirservers. So when there's
4903 a log complaint, it's for sure from a freshly uploaded descriptor.
4904 - When logging via syslog, include the pid whenever we provide
4905 a log entry. Suggested by Todd Fries.
4906 - When we're shutting down and we do something like try to post a
4907 server descriptor or rendezvous descriptor, don't complain that
4908 we seem to be unreachable. Of course we are, we're shutting down.
4909 - Change log line for unreachability to explicitly suggest /etc/hosts
4910 as the culprit. Also make it clearer what IP address and ports we're
4911 testing for reachability.
4912 - Put quotes around user-supplied strings when logging so users are
4913 more likely to realize if they add bad characters (like quotes)
4915 - NT service patch from Matt Edman to improve error messages on Win32.
4918 Changes in version 0.1.0.17 - 2006-02-17
4919 o Crash bugfixes on 0.1.0.x:
4920 - When servers with a non-zero DirPort came out of hibernation,
4921 sometimes they would trigger an assert.
4923 o Other important bugfixes:
4924 - On platforms that don't have getrlimit (like Windows), we were
4925 artificially constraining ourselves to a max of 1024
4926 connections. Now just assume that we can handle as many as 15000
4927 connections. Hopefully this won't cause other problems.
4929 o Backported features:
4930 - When we're a server, a client asks for an old-style directory,
4931 and our write bucket is empty, don't give it to him. This way
4932 small servers can continue to serve the directory *sometimes*,
4933 without getting overloaded.
4934 - Whenever you get a 503 in response to a directory fetch, try
4935 once more. This will become important once servers start sending
4936 503's whenever they feel busy.
4937 - Fetch a new directory every 120 minutes, not every 40 minutes.
4938 Now that we have hundreds of thousands of users running the old
4939 directory algorithm, it's starting to hurt a lot.
4940 - Bump up the period for forcing a hidden service descriptor upload
4941 from 20 minutes to 1 hour.
4944 Changes in version 0.1.0.16 - 2006-01-02
4945 o Crash bugfixes on 0.1.0.x:
4946 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
4947 corrupting the heap, losing FDs, or crashing when we need to resize
4948 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
4949 - It turns out sparc64 platforms crash on unaligned memory access
4950 too -- so detect and avoid this.
4951 - Handle truncated compressed data correctly (by detecting it and
4953 - Fix possible-but-unlikely free(NULL) in control.c.
4954 - When we were closing connections, there was a rare case that
4955 stomped on memory, triggering seg faults and asserts.
4956 - Avoid potential infinite recursion when building a descriptor. (We
4957 don't know that it ever happened, but better to fix it anyway.)
4958 - We were neglecting to unlink marked circuits from soon-to-close OR
4959 connections, which caused some rare scribbling on freed memory.
4960 - Fix a memory stomping race bug when closing the joining point of two
4961 rendezvous circuits.
4962 - Fix an assert in time parsing found by Steven Murdoch.
4964 o Other bugfixes on 0.1.0.x:
4965 - When we're doing reachability testing, provide more useful log
4966 messages so the operator knows what to expect.
4967 - Do not check whether DirPort is reachable when we are suppressing
4968 advertising it because of hibernation.
4969 - When building with -static or on Solaris, we sometimes needed -ldl.
4970 - One of the dirservers (tor26) changed its IP address.
4971 - When we're deciding whether a stream has enough circuits around
4972 that can handle it, count the freshly dirty ones and not the ones
4973 that are so dirty they won't be able to handle it.
4974 - When we're expiring old circuits, we had a logic error that caused
4975 us to close new rendezvous circuits rather than old ones.
4976 - Give a more helpful log message when you try to change ORPort via
4977 the controller: you should upgrade Tor if you want that to work.
4978 - We were failing to parse Tor versions that start with "Tor ".
4979 - Tolerate faulty streams better: when a stream fails for reason
4980 exitpolicy, stop assuming that the router is lying about his exit
4981 policy. When a stream fails for reason misc, allow it to retry just
4982 as if it was resolvefailed. When a stream has failed three times,
4983 reset its failure count so we can try again and get all three tries.
4986 Changes in version 0.1.0.15 - 2005-09-23
4987 o Bugfixes on 0.1.0.x:
4988 - Reject ports 465 and 587 (spam targets) in default exit policy.
4989 - Don't crash when we don't have any spare file descriptors and we
4990 try to spawn a dns or cpu worker.
4991 - Get rid of IgnoreVersion undocumented config option, and make us
4992 only warn, never exit, when we're running an obsolete version.
4993 - Don't try to print a null string when your server finds itself to
4994 be unreachable and the Address config option is empty.
4995 - Make the numbers in read-history and write-history into uint64s,
4996 so they don't overflow and publish negatives in the descriptor.
4997 - Fix a minor memory leak in smartlist_string_remove().
4998 - We were only allowing ourselves to upload a server descriptor at
4999 most every 20 minutes, even if it changed earlier than that.
5000 - Clean up log entries that pointed to old URLs.
5003 Changes in version 0.1.0.14 - 2005-08-08
5004 o Bugfixes on 0.1.0.x:
5005 - Fix the other half of the bug with crypto handshakes
5007 - Fix an assert trigger if you send a 'signal term' via the
5008 controller when it's listening for 'event info' messages.
5011 Changes in version 0.1.0.13 - 2005-08-04
5012 o Bugfixes on 0.1.0.x:
5013 - Fix a critical bug in the security of our crypto handshakes.
5014 - Fix a size_t underflow in smartlist_join_strings2() that made
5015 it do bad things when you hand it an empty smartlist.
5016 - Fix Windows installer to ship Tor license (thanks to Aphex for
5017 pointing out this oversight) and put a link to the doc directory
5019 - Explicitly set no-unaligned-access for sparc: it turns out the
5020 new gcc's let you compile broken code, but that doesn't make it
5024 Changes in version 0.1.0.12 - 2005-07-18
5025 o New directory servers:
5026 - tor26 has changed IP address.
5028 o Bugfixes on 0.1.0.x:
5029 - Fix a possible double-free in tor_gzip_uncompress().
5030 - When --disable-threads is set, do not search for or link against
5032 - Don't trigger an assert if an authoritative directory server
5033 claims its dirport is 0.
5034 - Fix bug with removing Tor as an NT service: some people were
5035 getting "The service did not return an error." Thanks to Matt
5039 Changes in version 0.1.0.11 - 2005-06-30
5040 o Bugfixes on 0.1.0.x:
5041 - Fix major security bug: servers were disregarding their
5042 exit policies if clients behaved unexpectedly.
5043 - Make OS X init script check for missing argument, so we don't
5044 confuse users who invoke it incorrectly.
5045 - Fix a seg fault in "tor --hash-password foo".
5046 - The MAPADDRESS control command was broken.
5049 Changes in version 0.1.0.10 - 2005-06-14
5051 - Make NT services work and start on startup on Win32 (based on
5052 patch by Matt Edman). See the FAQ entry for details.
5053 - Make 'platform' string in descriptor more accurate for Win32
5054 servers, so it's not just "unknown platform".
5055 - REUSEADDR on normal platforms means you can rebind to the port
5056 right after somebody else has let it go. But REUSEADDR on Win32
5057 means you can bind to the port _even when somebody else already
5058 has it bound_! So, don't do that on Win32.
5059 - Clean up the log messages when starting on Win32 with no config
5061 - Allow seeding the RNG on Win32 even when you're not running as
5062 Administrator. If seeding the RNG on Win32 fails, quit.
5064 o Assert / crash bugs:
5065 - Refuse relay cells that claim to have a length larger than the
5066 maximum allowed. This prevents a potential attack that could read
5067 arbitrary memory (e.g. keys) from an exit server's process
5069 - If unofficial Tor clients connect and send weird TLS certs, our
5070 Tor server triggers an assert. Stop asserting, and start handling
5071 TLS errors better in other situations too.
5072 - Fix a race condition that can trigger an assert when we have a
5073 pending create cell and an OR connection attempt fails.
5076 - Use pthreads for worker processes rather than forking. This was
5077 forced because when we forked, we ended up wasting a lot of
5078 duplicate ram over time.
5079 - Also switch to foo_r versions of some library calls to allow
5080 reentry and threadsafeness.
5081 - Implement --disable-threads configure option. Disable threads on
5082 netbsd and openbsd by default, because they have no reentrant
5083 resolver functions (!), and on solaris since it has other
5085 - Fix possible bug on threading platforms (e.g. win32) which was
5086 leaking a file descriptor whenever a cpuworker or dnsworker died.
5087 - Fix a minor memory leak when somebody establishes an introduction
5088 point at your Tor server.
5089 - Fix possible memory leak in tor_lookup_hostname(). (Thanks to
5091 - Add ./configure --with-dmalloc option, to track memory leaks.
5092 - And try to free all memory on closing, so we can detect what
5095 o Protocol correctness:
5096 - When we've connected to an OR and handshaked but didn't like
5097 the result, we were closing the conn without sending destroy
5098 cells back for pending circuits. Now send those destroys.
5099 - Start sending 'truncated' cells back rather than destroy cells
5100 if the circuit closes in front of you. This means we won't have
5101 to abandon partially built circuits.
5102 - Handle changed router status correctly when dirserver reloads
5103 fingerprint file. We used to be dropping all unverified descriptors
5104 right then. The bug was hidden because we would immediately
5105 fetch a directory from another dirserver, which would include the
5106 descriptors we just dropped.
5107 - Revise tor-spec to add more/better stream end reasons.
5108 - Revise all calls to connection_edge_end to avoid sending 'misc',
5109 and to take errno into account where possible.
5110 - Client now retries when streams end early for 'hibernating' or
5111 'resource limit' reasons, rather than failing them.
5112 - Try to be more zealous about calling connection_edge_end when
5113 things go bad with edge conns in connection.c.
5115 o Robustness improvements:
5116 - Better handling for heterogeneous / unreliable nodes:
5117 - Annotate circuits with whether they aim to contain high uptime
5118 nodes and/or high capacity nodes. When building circuits, choose
5120 - This means that every single node in an intro rend circuit,
5121 not just the last one, will have a minimum uptime.
5122 - New config option LongLivedPorts to indicate application streams
5123 that will want high uptime circuits.
5124 - Servers reset uptime when a dir fetch entirely fails. This
5125 hopefully reflects stability of the server's network connectivity.
5126 - If somebody starts his tor server in Jan 2004 and then fixes his
5127 clock, don't make his published uptime be a year.
5128 - Reset published uptime when we wake up from hibernation.
5129 - Introduce a notion of 'internal' circs, which are chosen without
5130 regard to the exit policy of the last hop. Intro and rendezvous
5131 circs must be internal circs, to avoid leaking information. Resolve
5132 and connect streams can use internal circs if they want.
5133 - New circuit pooling algorithm: keep track of what destination ports
5134 we've used recently (start out assuming we'll want to use 80), and
5135 make sure to have enough circs around to satisfy these ports. Also
5136 make sure to have 2 internal circs around if we've required internal
5137 circs lately (and with high uptime if we've seen that lately too).
5138 - Turn addr_policy_compare from a tristate to a quadstate; this should
5139 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
5140 for google.com" problem.
5141 - When a client asks us for a dir mirror and we don't have one,
5142 launch an attempt to get a fresh one.
5143 - First cut at support for "create-fast" cells. Clients can use
5144 these when extending to their first hop, since the TLS already
5145 provides forward secrecy and authentication. Not enabled on
5148 o Reachability testing.
5149 - Your Tor server will automatically try to see if its ORPort and
5150 DirPort are reachable from the outside, and it won't upload its
5151 descriptor until it decides at least ORPort is reachable (when
5152 DirPort is not yet found reachable, publish it as zero).
5153 - When building testing circs for ORPort testing, use only
5154 high-bandwidth nodes, so fewer circuits fail.
5155 - Notice when our IP changes, and reset stats/uptime/reachability.
5156 - Authdirservers don't do ORPort reachability detection, since
5157 they're in clique mode, so it will be rare to find a server not
5158 already connected to them.
5159 - Authdirservers now automatically approve nodes running 0.1.0.2-rc
5163 - Now we allow two unverified servers with the same nickname
5164 but different keys. But if a nickname is verified, only that
5165 nickname+key are allowed.
5166 - If you're an authdirserver connecting to an address:port,
5167 and it's not the OR you were expecting, forget about that
5168 descriptor. If he *was* the one you were expecting, then forget
5169 about all other descriptors for that address:port.
5170 - Allow servers to publish descriptors from 12 hours in the future.
5171 Corollary: only whine about clock skew from the dirserver if
5172 he's a trusted dirserver (since now even verified servers could
5173 have quite wrong clocks).
5174 - Require servers that use the default dirservers to have public IP
5175 addresses. We have too many servers that are configured with private
5176 IPs and their admins never notice the log entries complaining that
5177 their descriptors are being rejected.
5179 o Efficiency improvements:
5180 - Use libevent. Now we can use faster async cores (like epoll, kpoll,
5181 and /dev/poll), and hopefully work better on Windows too.
5182 - Apple's OS X 10.4.0 ships with a broken kqueue API, and using
5183 kqueue on 10.3.9 causes kernel panics. Don't use kqueue on OS X.
5184 - Find libevent even if it's hiding in /usr/local/ and your
5185 CFLAGS and LDFLAGS don't tell you to look there.
5186 - Be able to link with libevent as a shared library (the default
5187 after 1.0d), even if it's hiding in /usr/local/lib and even
5188 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
5189 assuming you're running gcc. Otherwise fail and give a useful
5191 - Switch to a new buffer management algorithm, which tries to avoid
5192 reallocing and copying quite as much. In first tests it looks like
5193 it uses *more* memory on average, but less cpu.
5194 - Switch our internal buffers implementation to use a ring buffer,
5195 to hopefully improve performance for fast servers a lot.
5196 - Reenable the part of the code that tries to flush as soon as an
5197 OR outbuf has a full TLS record available. Perhaps this will make
5198 OR outbufs not grow as huge except in rare cases, thus saving lots
5199 of CPU time plus memory.
5200 - Improve performance for dirservers: stop re-parsing the whole
5201 directory every time you regenerate it.
5202 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
5203 it much faster to look up a circuit for each relay cell.
5204 - Remove most calls to assert_all_pending_dns_resolves_ok(),
5205 since they're eating our cpu on exit nodes.
5206 - Stop wasting time doing a case insensitive comparison for every
5207 dns name every time we do any lookup. Canonicalize the names to
5208 lowercase when you first see them.
5211 - Handle unavailable hidden services better. Handle slow or busy
5212 hidden services better.
5213 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
5214 circ as necessary, if there are any completed ones lying around
5215 when we try to launch one.
5216 - Make hidden services try to establish a rendezvous for 30 seconds
5217 after fetching the descriptor, rather than for n (where n=3)
5218 attempts to build a circuit.
5219 - Adjust maximum skew and age for rendezvous descriptors: let skew
5220 be 48 hours rather than 90 minutes.
5221 - Reject malformed .onion addresses rather then passing them on as
5222 normal web requests.
5225 - More Tor controller support. See
5226 http://tor.eff.org/doc/control-spec.txt for all the new features,
5227 including signals to emulate unix signals from any platform;
5228 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
5229 closestream; closecircuit; etc.
5230 - Encode hashed controller passwords in hex instead of base64,
5231 to make it easier to write controllers.
5232 - Revise control spec and implementation to allow all log messages to
5233 be sent to controller with their severities intact (suggested by
5234 Matt Edman). Disable debug-level logs while delivering a debug-level
5235 log to the controller, to prevent loop. Update TorControl to handle
5236 new log event types.
5238 o New config options/defaults:
5239 - Begin scrubbing sensitive strings from logs by default. Turn off
5240 the config option SafeLogging if you need to do debugging.
5241 - New exit policy: accept most low-numbered ports, rather than
5242 rejecting most low-numbered ports.
5243 - Put a note in the torrc about abuse potential with the default
5245 - Add support for CONNECTing through https proxies, with "HttpsProxy"
5247 - Add HttpProxyAuthenticator and HttpsProxyAuthenticator support
5248 based on patch from Adam Langley (basic auth only).
5249 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
5250 the fast servers that have been joining lately. (Clients are now
5251 willing to load balance over up to 2 MB of advertised bandwidth
5253 - New config option MaxAdvertisedBandwidth which lets you advertise
5254 a low bandwidthrate (to not attract as many circuits) while still
5255 allowing a higher bandwidthrate in reality.
5256 - Require BandwidthRate to be at least 20kB/s for servers.
5257 - Add a NoPublish config option, so you can be a server (e.g. for
5258 testing running Tor servers in other Tor networks) without
5259 publishing your descriptor to the primary dirservers.
5260 - Add a new AddressMap config directive to rewrite incoming socks
5261 addresses. This lets you, for example, declare an implicit
5262 required exit node for certain sites.
5263 - Add a new TrackHostExits config directive to trigger addressmaps
5264 for certain incoming socks addresses -- for sites that break when
5265 your exit keeps changing (based on patch from Mike Perry).
5266 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
5267 which describes how often we retry making new circuits if current
5268 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
5269 how long we're willing to make use of an already-dirty circuit.
5270 - Change compiled-in SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to
5271 a config option "ShutdownWaitLength" (when using kill -INT on
5273 - Fix an edge case in parsing config options: if they say "--"
5274 on the commandline, it's not a config option (thanks weasel).
5275 - New config option DirAllowPrivateAddresses for authdirservers.
5276 Now by default they refuse router descriptors that have non-IP or
5277 private-IP addresses.
5278 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
5279 smart" default value: low for servers and high for clients.
5280 - Some people were putting "Address " in their torrc, and they had
5281 a buggy resolver that resolved " " to 0.0.0.0. Oops.
5282 - If DataDir is ~/.tor, and that expands to /.tor, then default to
5283 LOCALSTATEDIR/tor instead.
5284 - Implement --verify-config command-line option to check if your torrc
5285 is valid without actually launching Tor.
5287 o Logging improvements:
5288 - When dirservers refuse a server descriptor, we now log its
5289 contactinfo, platform, and the poster's IP address.
5290 - Only warn once per nickname from add_nickname_list_to_smartlist()
5291 per failure, so an entrynode or exitnode choice that's down won't
5293 - When we're connecting to an OR and he's got a different nickname/key
5294 than we were expecting, only complain loudly if we're an OP or a
5295 dirserver. Complaining loudly to the OR admins just confuses them.
5296 - Whine at you if you're a server and you don't set your contactinfo.
5297 - Warn when exit policy implicitly allows local addresses.
5298 - Give a better warning when some other server advertises an
5299 ORPort that is actually an apache running ssl.
5300 - If we get an incredibly skewed timestamp from a dirserver mirror
5301 that isn't a verified OR, don't warn -- it's probably him that's
5303 - When a dirserver causes you to give a warn, mention which dirserver
5305 - Initialize libevent later in the startup process, so the logs are
5306 already established by the time we start logging libevent warns.
5307 - Use correct errno on win32 if libevent fails.
5308 - Check and warn about known-bad/slow libevent versions.
5309 - Stop warning about sigpipes in the logs. We're going to
5310 pretend that getting these occassionally is normal and fine.
5312 o New contrib scripts:
5313 - New experimental script tor/contrib/exitlist: a simple python
5314 script to parse directories and find Tor nodes that exit to listed
5316 - New experimental script tor/contrib/ExerciseServer.py (needs more
5317 work) that uses the controller interface to build circuits and
5318 fetch pages over them. This will help us bootstrap servers that
5319 have lots of capacity but haven't noticed it yet.
5320 - New experimental script tor/contrib/PathDemo.py (needs more work)
5321 that uses the controller interface to let you choose whole paths
5323 "<hostname>.<path,separated by dots>.<length of path>.path"
5324 - New contributed script "privoxy-tor-toggle" to toggle whether
5325 Privoxy uses Tor. Seems to be configured for Debian by default.
5326 - Have torctl.in/tor.sh.in check for location of su binary (needed
5330 - chdir() to your datadirectory at the *end* of the daemonize process,
5331 not the beginning. This was a problem because the first time you
5332 run tor, if your datadir isn't there, and you have runasdaemon set
5333 to 1, it will try to chdir to it before it tries to create it. Oops.
5334 - Fix several double-mark-for-close bugs, e.g. where we were finding
5335 a conn for a cell even if that conn is already marked for close.
5336 - Stop most cases of hanging up on a socks connection without sending
5338 - Fix a bug in the RPM package: set home directory for _tor to
5339 something more reasonable when first installing.
5340 - Stop putting nodename in the Platform string in server descriptors.
5341 It doesn't actually help, and it is confusing/upsetting some people.
5342 - When using preferred entry or exit nodes, ignore whether the
5343 circuit wants uptime or capacity. They asked for the nodes, they
5345 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
5346 artificially capped at 500kB.
5347 - Cache local dns resolves correctly even when they're .exit
5349 - If we're hibernating and we get a SIGINT, exit immediately.
5350 - tor-resolve requests were ignoring .exit if there was a working circuit
5351 they could use instead.
5352 - Pay more attention to the ClientOnly config option.
5353 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in certain
5354 installer screens; and don't put stuff into StartupItems unless
5355 the user asks you to.
5358 - Rewrite address "serifos.exit" to "externalIP.serifos.exit"
5359 rather than just rejecting it.
5360 - If our clock jumps forward by 100 seconds or more, assume something
5361 has gone wrong with our network and abandon all not-yet-used circs.
5362 - When an application is using socks5, give him the whole variety of
5363 potential socks5 responses (connect refused, host unreachable, etc),
5364 rather than just "success" or "failure".
5365 - A more sane version numbering system. See
5366 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
5367 - Change version parsing logic: a version is "obsolete" if it is not
5368 recommended and (1) there is a newer recommended version in the
5369 same series, or (2) there are no recommended versions in the same
5370 series, but there are some recommended versions in a newer series.
5371 A version is "new" if it is newer than any recommended version in
5373 - Report HTTP reasons to client when getting a response from directory
5374 servers -- so you can actually know what went wrong.
5375 - Reject odd-looking addresses at the client (e.g. addresses that
5376 contain a colon), rather than having the server drop them because
5378 - Stop publishing socksport in the directory, since it's not
5379 actually meant to be public. For compatibility, publish a 0 there
5381 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
5382 cookies to disk and doesn't log each web request to disk. (Thanks
5383 to Brett Carrington for pointing this out.)
5384 - Add OSX uninstall instructions. An actual uninstall script will
5386 - Add "opt hibernating 1" to server descriptor to make it clearer
5387 whether the server is hibernating.
5390 Changes in version 0.0.9.10 - 2005-06-16
5391 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
5392 - Refuse relay cells that claim to have a length larger than the
5393 maximum allowed. This prevents a potential attack that could read
5394 arbitrary memory (e.g. keys) from an exit server's process
5398 Changes in version 0.0.9.9 - 2005-04-23
5399 o Bugfixes on 0.0.9.x:
5400 - If unofficial Tor clients connect and send weird TLS certs, our
5401 Tor server triggers an assert. This release contains a minimal
5402 backport from the broader fix that we put into 0.1.0.4-rc.
5405 Changes in version 0.0.9.8 - 2005-04-07
5406 o Bugfixes on 0.0.9.x:
5407 - We have a bug that I haven't found yet. Sometimes, very rarely,
5408 cpuworkers get stuck in the 'busy' state, even though the cpuworker
5409 thinks of itself as idle. This meant that no new circuits ever got
5410 established. Here's a workaround to kill any cpuworker that's been
5411 busy for more than 100 seconds.
5414 Changes in version 0.0.9.7 - 2005-04-01
5415 o Bugfixes on 0.0.9.x:
5416 - Fix another race crash bug (thanks to Glenn Fink for reporting).
5417 - Compare identity to identity, not to nickname, when extending to
5418 a router not already in the directory. This was preventing us from
5419 extending to unknown routers. Oops.
5420 - Make sure to create OS X Tor user in <500 range, so we aren't
5421 creating actual system users.
5422 - Note where connection-that-hasn't-sent-end was marked, and fix
5423 a few really loud instances of this harmless bug (it's fixed more
5427 Changes in version 0.0.9.6 - 2005-03-24
5428 o Bugfixes on 0.0.9.x (crashes and asserts):
5429 - Add new end stream reasons to maintainance branch. Fix bug where
5430 reason (8) could trigger an assert. Prevent bug from recurring.
5431 - Apparently win32 stat wants paths to not end with a slash.
5432 - Fix assert triggers in assert_cpath_layer_ok(), where we were
5433 blowing away the circuit that conn->cpath_layer points to, then
5434 checking to see if the circ is well-formed. Backport check to make
5435 sure we dont use the cpath on a closed connection.
5436 - Prevent circuit_resume_edge_reading_helper() from trying to package
5437 inbufs for marked-for-close streams.
5438 - Don't crash on hup if your options->address has become unresolvable.
5439 - Some systems (like OS X) sometimes accept() a connection and tell
5440 you the remote host is 0.0.0.0:0. If this happens, due to some
5441 other mis-features, we get confused; so refuse the conn for now.
5443 o Bugfixes on 0.0.9.x (other):
5444 - Fix harmless but scary "Unrecognized content encoding" warn message.
5445 - Add new stream error reason: TORPROTOCOL reason means "you are not
5446 speaking a version of Tor I understand; say bye-bye to your stream."
5447 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
5448 into the future, now that we are more tolerant of skew. This
5449 resolves a bug where a Tor server would refuse to cache a directory
5450 because all the directories it gets are too far in the future;
5451 yet the Tor server never logs any complaints about clock skew.
5452 - Mac packaging magic: make man pages useable, and do not overwrite
5453 existing torrc files.
5454 - Make OS X log happily to /var/log/tor/tor.log
5457 Changes in version 0.0.9.5 - 2005-02-22
5458 o Bugfixes on 0.0.9.x:
5459 - Fix an assert race at exit nodes when resolve requests fail.
5460 - Stop picking unverified dir mirrors--it only leads to misery.
5461 - Patch from Matt Edman to make NT services work better. Service
5462 support is still not compiled into the executable by default.
5463 - Patch from Dmitri Bely so the Tor service runs better under
5464 the win32 SYSTEM account.
5465 - Make tor-resolve actually work (?) on Win32.
5466 - Fix a sign bug when getrlimit claims to have 4+ billion
5467 file descriptors available.
5468 - Stop refusing to start when bandwidthburst == bandwidthrate.
5469 - When create cells have been on the onion queue more than five
5470 seconds, just send back a destroy and take them off the list.
5473 Changes in version 0.0.9.4 - 2005-02-03
5474 o Bugfixes on 0.0.9:
5475 - Fix an assert bug that took down most of our servers: when
5476 a server claims to have 1 GB of bandwidthburst, don't
5478 - Don't crash as badly if we have spawned the max allowed number
5479 of dnsworkers, or we're out of file descriptors.
5480 - Block more file-sharing ports in the default exit policy.
5481 - MaxConn is now automatically set to the hard limit of max
5482 file descriptors we're allowed (ulimit -n), minus a few for
5484 - Give a clearer message when servers need to raise their
5485 ulimit -n when they start running out of file descriptors.
5486 - SGI Compatibility patches from Jan Schaumann.
5487 - Tolerate a corrupt cached directory better.
5488 - When a dirserver hasn't approved your server, list which one.
5489 - Go into soft hibernation after 95% of the bandwidth is used,
5490 not 99%. This is especially important for daily hibernators who
5491 have a small accounting max. Hopefully it will result in fewer
5492 cut connections when the hard hibernation starts.
5493 - Load-balance better when using servers that claim more than
5494 800kB/s of capacity.
5495 - Make NT services work (experimental, only used if compiled in).
5498 Changes in version 0.0.9.3 - 2005-01-21
5499 o Bugfixes on 0.0.9:
5500 - Backport the cpu use fixes from main branch, so busy servers won't
5501 need as much processor time.
5502 - Work better when we go offline and then come back, or when we
5503 run Tor at boot before the network is up. We do this by
5504 optimistically trying to fetch a new directory whenever an
5505 application request comes in and we think we're offline -- the
5506 human is hopefully a good measure of when the network is back.
5507 - Backport some minimal hidserv bugfixes: keep rend circuits open as
5508 long as you keep using them; actually publish hidserv descriptors
5509 shortly after they change, rather than waiting 20-40 minutes.
5510 - Enable Mac startup script by default.
5511 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
5512 - When you update AllowUnverifiedNodes or FirewallPorts via the
5513 controller's setconf feature, we were always appending, never
5515 - When you update HiddenServiceDir via setconf, it was screwing up
5516 the order of reading the lines, making it fail.
5517 - Do not rewrite a cached directory back to the cache; otherwise we
5518 will think it is recent and not fetch a newer one on startup.
5519 - Workaround for webservers that lie about Content-Encoding: Tor
5520 now tries to autodetect compressed directories and compression
5521 itself. This lets us Proxypass dir fetches through apache.
5524 Changes in version 0.0.9.2 - 2005-01-04
5525 o Bugfixes on 0.0.9 (crashes and asserts):
5526 - Fix an assert on startup when the disk is full and you're logging
5528 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
5529 style address, then we'd crash.
5530 - Fix an assert trigger when the running-routers string we get from
5531 a dirserver is broken.
5532 - Make worker threads start and run on win32. Now win32 servers
5534 - Bandaid (not actually fix, but now it doesn't crash) an assert
5535 where the dns worker dies mysteriously and the main Tor process
5536 doesn't remember anything about the address it was resolving.
5538 o Bugfixes on 0.0.9 (Win32):
5539 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
5540 name out of the warning/assert messages.
5541 - Fix a superficial "unhandled error on read" bug on win32.
5542 - The win32 installer no longer requires a click-through for our
5543 license, since our Free Software license grants rights but does not
5545 - Win32: When connecting to a dirserver fails, try another one
5546 immediately. (This was already working for non-win32 Tors.)
5547 - Stop trying to parse $HOME on win32 when hunting for default
5549 - Make tor-resolve.c work on win32 by calling network_init().
5551 o Bugfixes on 0.0.9 (other):
5552 - Make 0.0.9.x build on Solaris again.
5553 - Due to a fencepost error, we were blowing away the \n when reporting
5554 confvalue items in the controller. So asking for multiple config
5555 values at once couldn't work.
5556 - When listing circuits that are pending on an opening OR connection,
5557 if we're an OR we were listing circuits that *end* at us as
5558 being pending on every listener, dns/cpu worker, etc. Stop that.
5559 - Dirservers were failing to create 'running-routers' or 'directory'
5560 strings if we had more than some threshold of routers. Fix them so
5561 they can handle any number of routers.
5562 - Fix a superficial "Duplicate mark for close" bug.
5563 - Stop checking for clock skew for OR connections, even for servers.
5564 - Fix a fencepost error that was chopping off the last letter of any
5565 nickname that is the maximum allowed nickname length.
5566 - Update URLs in log messages so they point to the new website.
5567 - Fix a potential problem in mangling server private keys while
5568 writing to disk (not triggered yet, as far as we know).
5569 - Include the licenses for other free software we include in Tor,
5570 now that we're shipping binary distributions more regularly.
5573 Changes in version 0.0.9.1 - 2004-12-15
5574 o Bugfixes on 0.0.9:
5575 - Make hibernation actually work.
5576 - Make HashedControlPassword config option work.
5577 - When we're reporting event circuit status to a controller,
5578 don't use the stream status code.
5581 Changes in version 0.0.9 - 2004-12-12
5582 o Bugfixes on 0.0.8.1 (Crashes and asserts):
5583 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
5584 write() call will fail and we handle it there.
5585 - When we run out of disk space, or other log writing error, don't
5586 crash. Just stop logging to that log and continue.
5587 - Fix isspace() and friends so they still make Solaris happy
5588 but also so they don't trigger asserts on win32.
5589 - Fix assert failure on malformed socks4a requests.
5590 - Fix an assert bug where a hidden service provider would fail if
5591 the first hop of his rendezvous circuit was down.
5592 - Better handling of size_t vs int, so we're more robust on 64
5595 o Bugfixes on 0.0.8.1 (Win32):
5596 - Make windows sockets actually non-blocking (oops), and handle
5597 win32 socket errors better.
5598 - Fix parse_iso_time on platforms without strptime (eg win32).
5599 - win32: when being multithreaded, leave parent fdarray open.
5600 - Better handling of winsock includes on non-MSV win32 compilers.
5601 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
5603 - Make unit tests work on win32.
5605 o Bugfixes on 0.0.8.1 (Path selection and streams):
5606 - Calculate timeout for waiting for a connected cell from the time
5607 we sent the begin cell, not from the time the stream started. If
5608 it took a long time to establish the circuit, we would time out
5609 right after sending the begin cell.
5610 - Fix router_compare_addr_to_addr_policy: it was not treating a port
5611 of * as always matching, so we were picking reject *:* nodes as
5612 exit nodes too. Oops.
5613 - When read() failed on a stream, we would close it without sending
5614 back an end. So 'connection refused' would simply be ignored and
5615 the user would get no response.
5616 - Stop a sigpipe: when an 'end' cell races with eof from the app,
5617 we shouldn't hold-open-until-flush if the eof arrived first.
5618 - Let resolve conns retry/expire also, rather than sticking around
5620 - Fix more dns related bugs: send back resolve_failed and end cells
5621 more reliably when the resolve fails, rather than closing the
5622 circuit and then trying to send the cell. Also attach dummy resolve
5623 connections to a circuit *before* calling dns_resolve(), to fix
5624 a bug where cached answers would never be sent in RESOLVED cells.
5626 o Bugfixes on 0.0.8.1 (Circuits):
5627 - Finally fix a bug that's been plaguing us for a year:
5628 With high load, circuit package window was reaching 0. Whenever
5629 we got a circuit-level sendme, we were reading a lot on each
5630 socket, but only writing out a bit. So we would eventually reach
5631 eof. This would be noticed and acted on even when there were still
5632 bytes sitting in the inbuf.
5633 - Use identity comparison, not nickname comparison, to choose which
5634 half of circuit-ID-space each side gets to use. This is needed
5635 because sometimes we think of a router as a nickname, and sometimes
5636 as a hex ID, and we can't predict what the other side will do.
5638 o Bugfixes on 0.0.8.1 (Other):
5639 - Fix a whole slew of memory leaks.
5640 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
5641 - If we are using select, make sure we stay within FD_SETSIZE.
5642 - When poll() is interrupted, we shouldn't believe the revents values.
5643 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
5644 and smartlist_len, which are two major profiling offenders.
5645 - If do_hup fails, actually notice.
5646 - Flush the log file descriptor after we print "Tor opening log file",
5647 so we don't see those messages days later.
5648 - Hidden service operators now correctly handle version 1 style
5649 INTRODUCE1 cells (nobody generates them still, so not a critical
5651 - Handle more errnos from accept() without closing the listener.
5652 Some OpenBSD machines were closing their listeners because
5653 they ran out of file descriptors.
5654 - Some people had wrapped their tor client/server in a script
5655 that would restart it whenever it died. This did not play well
5656 with our "shut down if your version is obsolete" code. Now people
5657 don't fetch a new directory if their local cached version is
5659 - Make our autogen.sh work on ksh as well as bash.
5660 - Better torrc example lines for dirbindaddress and orbindaddress.
5661 - Improved bounds checking on parsed ints (e.g. config options and
5662 the ones we find in directories.)
5663 - Stop using separate defaults for no-config-file and
5664 empty-config-file. Now you have to explicitly turn off SocksPort,
5665 if you don't want it open.
5666 - We were starting to daemonize before we opened our logs, so if
5667 there were any problems opening logs, we would complain to stderr,
5668 which wouldn't work, and then mysteriously exit.
5669 - If a verified OR connects to us before he's uploaded his descriptor,
5670 or we verify him and hup but he still has the original TLS
5671 connection, then conn->nickname is still set like he's unverified.
5673 o Code security improvements, inspired by Ilja:
5674 - tor_snprintf wrapper over snprintf with consistent (though not C99)
5676 - Replace sprintf with tor_snprintf. (I think they were all safe, but
5678 - Replace strcpy/strncpy with strlcpy in more places.
5679 - Avoid strcat; use tor_snprintf or strlcat instead.
5681 o Features (circuits and streams):
5682 - New circuit building strategy: keep a list of ports that we've
5683 used in the past 6 hours, and always try to have 2 circuits open
5684 or on the way that will handle each such port. Seed us with port
5685 80 so web users won't complain that Tor is "slow to start up".
5686 - Make kill -USR1 dump more useful stats about circuits.
5687 - When warning about retrying or giving up, print the address, so
5688 the user knows which one it's talking about.
5689 - If you haven't used a clean circuit in an hour, throw it away,
5690 just to be on the safe side. (This means after 6 hours a totally
5691 unused Tor client will have no circuits open.)
5692 - Support "foo.nickname.exit" addresses, to let Alice request the
5693 address "foo" as viewed by exit node "nickname". Based on a patch
5695 - If your requested entry or exit node has advertised bandwidth 0,
5697 - Be more greedy about filling up relay cells -- we try reading again
5698 once we've processed the stuff we read, in case enough has arrived
5699 to fill the last cell completely.
5700 - Refuse application socks connections to port 0.
5701 - Use only 0.0.9pre1 and later servers for resolve cells.
5703 o Features (bandwidth):
5704 - Hibernation: New config option "AccountingMax" lets you
5705 set how many bytes per month (in each direction) you want to
5706 allow your server to consume. Rather than spreading those
5707 bytes out evenly over the month, we instead hibernate for some
5708 of the month and pop up at a deterministic time, work until
5709 the bytes are consumed, then hibernate again. Config option
5710 "MonthlyAccountingStart" lets you specify which day of the month
5711 your billing cycle starts on.
5712 - Implement weekly/monthly/daily accounting: now you specify your
5713 hibernation properties by
5714 AccountingMax N bytes|KB|MB|GB|TB
5715 AccountingStart day|week|month [day] HH:MM
5716 Defaults to "month 1 0:00".
5717 - Let bandwidth and interval config options be specified as 5 bytes,
5718 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
5720 o Features (directories):
5721 - New "router-status" line in directory, to better bind each verified
5722 nickname to its identity key.
5723 - Clients can ask dirservers for /dir.z to get a compressed version
5724 of the directory. Only works for servers running 0.0.9, of course.
5725 - Make clients cache directories and use them to seed their router
5726 lists at startup. This means clients have a datadir again.
5727 - Respond to content-encoding headers by trying to uncompress as
5729 - Clients and servers now fetch running-routers; cache
5730 running-routers; compress running-routers; serve compressed
5732 - Make moria2 advertise a dirport of 80, so people behind firewalls
5733 will be able to get a directory.
5734 - Http proxy support
5735 - Dirservers translate requests for http://%s:%d/x to /x
5736 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
5737 be routed through this host.
5738 - Clients ask for /tor/x rather than /x for new enough dirservers.
5739 This way we can one day coexist peacefully with apache.
5740 - Clients specify a "Host: %s%d" http header, to be compatible
5741 with more proxies, and so running squid on an exit node can work.
5742 - Protect dirservers from overzealous descriptor uploading -- wait
5743 10 seconds after directory gets dirty, before regenerating.
5745 o Features (packages and install):
5746 - Add NSI installer contributed by J Doe.
5747 - Apply NT service patch from Osamu Fujino. Still needs more work.
5748 - Commit VC6 and VC7 workspace/project files.
5749 - Commit a tor.spec for making RPM files, with help from jbash.
5750 - Add contrib/torctl.in contributed by Glenn Fink.
5751 - Make expand_filename handle ~ and ~username.
5752 - Use autoconf to enable largefile support where necessary. Use
5753 ftello where available, since ftell can fail at 2GB.
5754 - Ship src/win32/ in the tarball, so people can use it to build.
5755 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
5758 o Features (ui controller):
5759 - Control interface: a separate program can now talk to your
5760 client/server over a socket, and get/set config options, receive
5761 notifications of circuits and streams starting/finishing/dying,
5762 bandwidth used, etc. The next step is to get some GUIs working.
5763 Let us know if you want to help out. See doc/control-spec.txt .
5764 - Ship a contrib/tor-control.py as an example script to interact
5765 with the control port.
5766 - "tor --hash-password zzyxz" will output a salted password for
5767 use in authenticating to the control interface.
5768 - Implement the control-spec's SAVECONF command, to write your
5769 configuration to torrc.
5770 - Get cookie authentication for the controller closer to working.
5771 - When set_conf changes our server descriptor, upload a new copy.
5772 But don't upload it too often if there are frequent changes.
5774 o Features (config and command-line):
5775 - Deprecate unofficial config option abbreviations, and abbreviations
5776 not on the command line.
5777 - Configuration infrastructure support for warning on obsolete
5779 - Give a slightly more useful output for "tor -h".
5780 - Break DirFetchPostPeriod into:
5781 - DirFetchPeriod for fetching full directory,
5782 - StatusFetchPeriod for fetching running-routers,
5783 - DirPostPeriod for posting server descriptor,
5784 - RendPostPeriod for posting hidden service descriptors.
5785 - New log format in config:
5786 "Log minsev[-maxsev] stdout|stderr|syslog" or
5787 "Log minsev[-maxsev] file /var/foo"
5788 - DirPolicy config option, to let people reject incoming addresses
5789 from their dirserver.
5790 - "tor --list-fingerprint" will list your identity key fingerprint
5792 - Make tor --version --version dump the cvs Id of every file.
5793 - New 'MyFamily nick1,...' config option for a server to
5794 specify other servers that shouldn't be used in the same circuit
5795 with it. Only believed if nick1 also specifies us.
5796 - New 'NodeFamily nick1,nick2,...' config option for a client to
5797 specify nodes that it doesn't want to use in the same circuit.
5798 - New 'Redirectexit pattern address:port' config option for a
5799 server to redirect exit connections, e.g. to a local squid.
5800 - Add "pass" target for RedirectExit, to make it easier to break
5801 out of a sequence of RedirectExit rules.
5802 - Make the dirservers file obsolete.
5803 - Include a dir-signing-key token in directories to tell the
5804 parsing entity which key is being used to sign.
5805 - Remove the built-in bulky default dirservers string.
5806 - New config option "Dirserver %s:%d [fingerprint]", which can be
5807 repeated as many times as needed. If no dirservers specified,
5808 default to moria1,moria2,tor26.
5809 - Make 'Routerfile' config option obsolete.
5810 - Discourage people from setting their dirfetchpostperiod more often
5811 than once per minute.
5814 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
5815 get back to normal.)
5816 - Accept *:706 (silc) in default exit policy.
5817 - Implement new versioning format for post 0.1.
5818 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
5819 log more informatively.
5820 - Check clock skew for verified servers, but allow unverified
5821 servers and clients to have any clock skew.
5822 - Make sure the hidden service descriptors are at a random offset
5823 from each other, to hinder linkability.
5824 - Clients now generate a TLS cert too, in preparation for having
5825 them act more like real nodes.
5826 - Add a pure-C tor-resolve implementation.
5827 - Use getrlimit and friends to ensure we can reach MaxConn (currently
5828 1024) file descriptors.
5829 - Raise the max dns workers from 50 to 100.
5832 Changes in version 0.0.8.1 - 2004-10-13
5834 - Fix a seg fault that can be triggered remotely for Tor
5835 clients/servers with an open dirport.
5836 - Fix a rare assert trigger, where routerinfos for entries in
5837 our cpath would expire while we're building the path.
5838 - Fix a bug in OutboundBindAddress so it (hopefully) works.
5839 - Fix a rare seg fault for people running hidden services on
5840 intermittent connections.
5841 - Fix a bug in parsing opt keywords with objects.
5842 - Fix a stale pointer assert bug when a stream detaches and
5844 - Fix a string format vulnerability (probably not exploitable)
5845 in reporting stats locally.
5846 - Fix an assert trigger: sometimes launching circuits can fail
5847 immediately, e.g. because too many circuits have failed recently.
5848 - Fix a compile warning on 64 bit platforms.
5851 Changes in version 0.0.8 - 2004-08-25
5853 - Made our unit tests compile again on OpenBSD 3.5, and tor
5854 itself compile again on OpenBSD on a sparc64.
5855 - We were neglecting milliseconds when logging on win32, so
5856 everything appeared to happen at the beginning of each second.
5857 - Check directory signature _before_ you decide whether you're
5858 you're running an obsolete version and should exit.
5859 - Check directory signature _before_ you parse the running-routers
5860 list to decide who's running.
5861 - Check return value of fclose while writing to disk, so we don't
5862 end up with broken files when servers run out of disk space.
5863 - Port it to SunOS 5.9 / Athena
5864 - Fix two bugs in saving onion keys to disk when rotating, so
5865 hopefully we'll get fewer people using old onion keys.
5866 - Remove our mostly unused -- and broken -- hex_encode()
5867 function. Use base16_encode() instead. (Thanks to Timo Lindfors
5868 for pointing out this bug.)
5869 - Only pick and establish intro points after we've gotten a
5871 - Fix assert triggers: if the other side returns an address 0.0.0.0,
5872 don't put it into the client dns cache.
5873 - If a begin failed due to exit policy, but we believe the IP
5874 address should have been allowed, switch that router to exitpolicy
5875 reject *:* until we get our next directory.
5878 - 'Extend' relay cell payloads now include the digest of the
5879 intended next hop's identity key. Now we can verify that we're
5880 extending to the right router, and also extend to routers we
5881 hadn't heard of before.
5884 - Tor nodes can now act as relays (with an advertised ORPort)
5885 without being manually verified by the dirserver operators.
5886 - Uploaded descriptors of unverified routers are now accepted
5887 by the dirservers, and included in the directory.
5888 - Verified routers are listed by nickname in the running-routers
5889 list; unverified routers are listed as "$<fingerprint>".
5890 - We now use hash-of-identity-key in most places rather than
5891 nickname or addr:port, for improved security/flexibility.
5892 - AllowUnverifiedNodes config option to let circuits choose no-name
5893 routers in entry,middle,exit,introduction,rendezvous positions.
5894 Allow middle and rendezvous positions by default.
5895 - When picking unverified routers, skip those with low uptime and/or
5896 low bandwidth, depending on what properties you care about.
5897 - ClientOnly option for nodes that never want to become servers.
5898 - Directory caching.
5899 - "AuthoritativeDir 1" option for the official dirservers.
5900 - Now other nodes (clients and servers) will cache the latest
5901 directory they've pulled down.
5902 - They can enable their DirPort to serve it to others.
5903 - Clients will pull down a directory from any node with an open
5904 DirPort, and check the signature/timestamp correctly.
5905 - Authoritative dirservers now fetch directories from other
5906 authdirservers, to stay better synced.
5907 - Running-routers list tells who's down also, along with noting
5908 if they're verified (listed by nickname) or unverified (listed
5910 - Allow dirservers to serve running-router list separately.
5911 This isn't used yet.
5912 - You can now fetch $DIRURL/running-routers to get just the
5913 running-routers line, not the whole descriptor list. (But
5914 clients don't use this yet.)
5915 - Clients choose nodes proportional to advertised bandwidth.
5916 - Clients avoid using nodes with low uptime as introduction points.
5917 - Handle servers with dynamic IP addresses: don't just replace
5918 options->Address with the resolved one at startup, and
5919 detect our address right before we make a routerinfo each time.
5920 - 'FascistFirewall' option to pick dirservers and ORs on specific
5921 ports; plus 'FirewallPorts' config option to tell FascistFirewall
5922 which ports are open. (Defaults to 80,443)
5923 - Try other dirservers immediately if the one you try is down. This
5924 should tolerate down dirservers better now.
5925 - ORs connect-on-demand to other ORs
5926 - If you get an extend cell to an OR you're not connected to,
5927 connect, handshake, and forward the create cell.
5928 - The authoritative dirservers stay connected to everybody,
5929 and everybody stays connected to 0.0.7 servers, but otherwise
5930 clients/servers expire unused connections after 5 minutes.
5931 - When servers get a sigint, they delay 30 seconds (refusing new
5932 connections) then exit. A second sigint causes immediate exit.
5933 - File and name management:
5934 - Look for .torrc if no CONFDIR "torrc" is found.
5935 - If no datadir is defined, then choose, make, and secure ~/.tor
5937 - If torrc not found, exitpolicy reject *:*.
5938 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
5939 - If no nickname is defined, derive default from hostname.
5940 - Rename secret key files, e.g. identity.key -> secret_id_key,
5941 to discourage people from mailing their identity key to tor-ops.
5942 - Refuse to build a circuit before the directory has arrived --
5943 it won't work anyway, since you won't know the right onion keys
5945 - Parse tor version numbers so we can do an is-newer-than check
5946 rather than an is-in-the-list check.
5947 - New socks command 'resolve', to let us shim gethostbyname()
5949 - A 'tor_resolve' script to access the socks resolve functionality.
5950 - A new socks-extensions.txt doc file to describe our
5951 interpretation and extensions to the socks protocols.
5952 - Add a ContactInfo option, which gets published in descriptor.
5953 - Write tor version at the top of each log file
5954 - New docs in the tarball:
5956 - Document that you should proxy your SSL traffic too.
5957 - Log a warning if the user uses an unsafe socks variant, so people
5958 are more likely to learn about privoxy or socat.
5959 - Log a warning if you're running an unverified server, to let you
5960 know you might want to get it verified.
5961 - Change the default exit policy to reject the default edonkey,
5962 kazaa, gnutella ports.
5963 - Add replace_file() to util.[ch] to handle win32's rename().
5964 - Publish OR uptime in descriptor (and thus in directory) too.
5965 - Remember used bandwidth (both in and out), and publish 15-minute
5966 snapshots for the past day into our descriptor.
5967 - Be more aggressive about trying to make circuits when the network
5968 has changed (e.g. when you unsuspend your laptop).
5969 - Check for time skew on http headers; report date in response to
5971 - If the entrynode config line has only one node, don't pick it as
5973 - Add strict{entry|exit}nodes config options. If set to 1, then
5974 we refuse to build circuits that don't include the specified entry
5976 - OutboundBindAddress config option, to bind to a specific
5977 IP address for outgoing connect()s.
5978 - End truncated log entries (e.g. directories) with "[truncated]".
5981 Changes in version 0.0.7.3 - 2004-08-12
5982 o Stop dnsworkers from triggering an assert failure when you
5983 ask them to resolve the host "".
5986 Changes in version 0.0.7.2 - 2004-07-07
5987 o A better fix for the 0.0.0.0 problem, that will hopefully
5988 eliminate the remaining related assertion failures.
5991 Changes in version 0.0.7.1 - 2004-07-04
5992 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
5993 since internally we use 0.0.0.0 to signify "not yet resolved".
5996 Changes in version 0.0.7 - 2004-06-07
5997 o Fixes for crashes and other obnoxious bugs:
5998 - Fix an epipe bug: sometimes when directory connections failed
5999 to connect, we would give them a chance to flush before closing
6001 - When we detached from a circuit because of resolvefailed, we
6002 would immediately try the same circuit twice more, and then
6003 give up on the resolve thinking we'd tried three different
6005 - Limit the number of intro circuits we'll attempt to build for a
6006 hidden service per 15-minute period.
6007 - Check recommended-software string *early*, before actually parsing
6008 the directory. Thus we can detect an obsolete version and exit,
6009 even if the new directory format doesn't parse.
6010 o Fixes for security bugs:
6011 - Remember which nodes are dirservers when you startup, and if a
6012 random OR enables his dirport, don't automatically assume he's
6013 a trusted dirserver.
6015 - Directory connections were asking the wrong poll socket to
6016 start writing, and not asking themselves to start writing.
6017 - When we detached from a circuit because we sent a begin but
6018 didn't get a connected, we would use it again the first time;
6019 but after that we would correctly switch to a different one.
6020 - Stop warning when the first onion decrypt attempt fails; they
6021 will sometimes legitimately fail now that we rotate keys.
6022 - Override unaligned-access-ok check when $host_cpu is ia64 or
6023 arm. Apparently they allow it but the kernel whines.
6024 - Dirservers try to reconnect periodically too, in case connections
6026 - Fix some memory leaks in directory servers.
6027 - Allow backslash in Win32 filenames.
6028 - Made Tor build complain-free on FreeBSD, hopefully without
6029 breaking other BSD builds. We'll see.
6030 - Check directory signatures based on name of signer, not on whom
6031 we got the directory from. This will let us cache directories more
6033 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
6036 - Doxygen markup on all functions and global variables.
6037 - Make directory functions update routerlist, not replace it. So
6038 now directory disagreements are not so critical a problem.
6039 - Remove the upper limit on number of descriptors in a dirserver's
6040 directory (not that we were anywhere close).
6041 - Allow multiple logfiles at different severity ranges.
6042 - Allow *BindAddress to specify ":port" rather than setting *Port
6043 separately. Allow multiple instances of each BindAddress config
6044 option, so you can bind to multiple interfaces if you want.
6045 - Allow multiple exit policy lines, which are processed in order.
6046 Now we don't need that huge line with all the commas in it.
6047 - Enable accept/reject policies on SOCKS connections, so you can bind
6048 to 0.0.0.0 but still control who can use your OP.
6049 - Updated the man page to reflect these features.
6052 Changes in version 0.0.6.2 - 2004-05-16
6053 o Our integrity-checking digest was checking only the most recent cell,
6054 not the previous cells like we'd thought.
6055 Thanks to Stefan Mark for finding the flaw!
6058 Changes in version 0.0.6.1 - 2004-05-06
6059 o Fix two bugs in our AES counter-mode implementation (this affected
6060 onion-level stream encryption, but not TLS-level). It turns
6061 out we were doing something much more akin to a 16-character
6062 polyalphabetic cipher. Oops.
6063 Thanks to Stefan Mark for finding the flaw!
6064 o Retire moria3 as a directory server, and add tor26 as a directory
6068 Changes in version 0.0.6 - 2004-05-02
6070 - Hidden services and rendezvous points are implemented. Go to
6071 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
6072 hidden services. (This only works via a socks4a proxy such as
6073 Privoxy, and currently it's quite slow.)
6074 - We now rotate link (tls context) keys and onion keys.
6075 - CREATE cells now include oaep padding, so you can tell
6076 if you decrypted them correctly.
6077 - Retry stream correctly when we fail to connect because of
6078 exit-policy-reject (should try another) or can't-resolve-address.
6079 - When we hup a dirserver and we've *removed* a server from the
6080 approved-routers list, now we remove that server from the
6081 in-memory directories too.
6082 - Add bandwidthburst to server descriptor.
6083 - Directories now say which dirserver signed them.
6084 - Use a tor_assert macro that logs failed assertions too.
6085 - Since we don't support truncateds much, don't bother sending them;
6086 just close the circ.
6087 - Fetch randomness from /dev/urandom better (not via fopen/fread)
6088 - Better debugging for tls errors
6089 - Set Content-Type on the directory and hidserv descriptor.
6090 - Remove IVs from cipher code, since AES-ctr has none.
6092 - Fix an assert trigger for exit nodes that's been plaguing us since
6093 the days of 0.0.2prexx (thanks weasel!)
6094 - Fix a bug where we were closing tls connections intermittently.
6095 It turns out openssl keeps its errors around -- so if an error
6096 happens, and you don't ask about it, and then another openssl
6097 operation happens and succeeds, and you ask if there was an error,
6098 it tells you about the first error.
6099 - Fix a bug that's been lurking since 27 may 03 (!)
6100 When passing back a destroy cell, we would use the wrong circ id.
6101 - Don't crash if a conn that sent a begin has suddenly lost its circuit.
6102 - Some versions of openssl have an SSL_pending function that erroneously
6103 returns bytes when there is a non-application record pending.
6104 - Win32 fixes. Tor now compiles on win32 with no warnings/errors.
6105 o We were using an array of length zero in a few places.
6106 o Win32's gethostbyname can't resolve an IP to an IP.
6107 o Win32's close can't close a socket.
6108 o Handle windows socket errors correctly.
6110 - check for <sys/limits.h> so we build on FreeBSD again, and
6111 <machine/limits.h> for NetBSD.
6114 Changes in version 0.0.5 - 2004-03-30
6115 o Install torrc as torrc.sample -- we no longer clobber your
6117 o Fix mangled-state bug in directory fetching (was causing sigpipes).
6118 o Only build circuits after we've fetched the directory: clients were
6119 using only the directory servers before they'd fetched a directory.
6120 This also means longer startup time; so it goes.
6121 o Fix an assert trigger where an OP would fail to handshake, and we'd
6122 expect it to have a nickname.
6123 o Work around a tsocks bug: do a socks reject when AP connection dies
6124 early, else tsocks goes into an infinite loop.
6125 o Hold socks connection open until reply is flushed (if possible)
6126 o Make exit nodes resolve IPs to IPs immediately, rather than asking
6127 the dns farm to do it.
6128 o Fix c99 aliasing warnings in rephist.c
6129 o Don't include server descriptors that are older than 24 hours in the
6131 o Give socks 'reject' replies their whole 15s to attempt to flush,
6132 rather than seeing the 60s timeout and assuming the flush had failed.
6133 o Clean automake droppings from the cvs repository
6134 o Add in a 'notice' log level for things the operator should hear
6135 but that aren't warnings
6138 Changes in version 0.0.4 - 2004-03-26
6139 o When connecting to a dirserver or OR and the network is down,
6143 Changes in version 0.0.3 - 2004-03-26
6144 o Warn and fail if server chose a nickname with illegal characters
6145 o Port to Solaris and Sparc:
6146 - include missing header fcntl.h
6147 - have autoconf find -lsocket -lnsl automatically
6148 - deal with hardware word alignment
6149 - make uname() work (solaris has a different return convention)
6150 - switch from using signal() to sigaction()
6151 o Preliminary work on reputation system:
6152 - Keep statistics on success/fail of connect attempts; they're published
6153 by kill -USR1 currently.
6154 - Add a RunTesting option to try to learn link state by creating test
6155 circuits, even when SocksPort is off.
6156 - Remove unused open circuits when there are too many.
6159 Changes in version 0.0.2 - 2004-03-19
6160 - Include strlcpy and strlcat for safer string ops
6161 - define INADDR_NONE so we compile (but still not run) on solaris
6164 Changes in version 0.0.2pre27 - 2004-03-14
6166 - Allow internal tor networks (we were rejecting internal IPs,
6167 now we allow them if they're set explicitly).
6168 - And fix a few endian issues.
6171 Changes in version 0.0.2pre26 - 2004-03-14
6173 - If a stream times out after 15s without a connected cell, don't
6174 try that circuit again: try a new one.
6175 - Retry streams at most 4 times. Then give up.
6176 - When a dirserver gets a descriptor from an unknown router, it
6177 logs its fingerprint (so the dirserver operator can choose to
6178 accept it even without mail from the server operator).
6179 - Inform unapproved servers when we reject their descriptors.
6180 - Make tor build on Windows again. It works as a client, who knows
6182 - Clearer instructions in the torrc for how to set up a server.
6183 - Be more efficient about reading fd's when our global token bucket
6184 (used for rate limiting) becomes empty.
6186 - Stop asserting that computers always go forward in time. It's
6188 - When we sent a cell (e.g. destroy) and then marked an OR connection
6189 expired, we might close it before finishing a flush if the other
6190 side isn't reading right then.
6191 - Don't allow dirservers to start if they haven't defined
6193 - We were caching transient dns failures. Oops.
6194 - Prevent servers from publishing an internal IP as their address.
6195 - Address a strcat vulnerability in circuit.c
6198 Changes in version 0.0.2pre25 - 2004-03-04
6200 - Put the OR's IP in its router descriptor, not its fqdn. That way
6201 we'll stop being stalled by gethostbyname for nodes with flaky dns,
6204 - If the user typed in an address that didn't resolve, the server
6208 Changes in version 0.0.2pre24 - 2004-03-03
6210 - Fix an assertion failure in dns.c, where we were trying to dequeue
6211 a pending dns resolve even if it wasn't pending
6212 - Fix a spurious socks5 warning about still trying to write after the
6213 connection is finished.
6214 - Hold certain marked_for_close connections open until they're finished
6215 flushing, rather than losing bytes by closing them too early.
6216 - Correctly report the reason for ending a stream
6217 - Remove some duplicate calls to connection_mark_for_close
6218 - Put switch_id and start_daemon earlier in the boot sequence, so it
6219 will actually try to chdir() to options.DataDirectory
6220 - Make 'make test' exit(1) if a test fails; fix some unit tests
6221 - Make tor fail when you use a config option it doesn't know about,
6222 rather than warn and continue.
6223 - Make --version work
6224 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
6227 Changes in version 0.0.2pre23 - 2004-02-29
6229 - Print a statement when the first circ is finished, so the user
6231 - If a relay cell is unrecognized at the end of the circuit,
6232 send back a destroy. (So attacks to mutate cells are more
6234 - New config option 'excludenodes' to avoid certain nodes for circuits.
6235 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
6236 so you can collect coredumps there.
6238 - Fix a bug in tls flushing where sometimes data got wedged and
6239 didn't flush until more data got sent. Hopefully this bug was
6240 a big factor in the random delays we were seeing.
6241 - Make 'connected' cells include the resolved IP, so the client
6242 dns cache actually gets populated.
6243 - Disallow changing from ORPort=0 to ORPort>0 on hup.
6244 - When we time-out on a stream and detach from the circuit, send an
6245 end cell down it first.
6246 - Only warn about an unknown router (in exitnodes, entrynodes,
6247 excludenodes) after we've fetched a directory.
6250 Changes in version 0.0.2pre22 - 2004-02-26
6252 - Servers publish less revealing uname information in descriptors.
6253 - More memory tracking and assertions, to crash more usefully when
6255 - If the default torrc isn't there, just use some default defaults.
6256 Plus provide an internal dirservers file if they don't have one.
6257 - When the user tries to use Tor as an http proxy, give them an http
6258 501 failure explaining that we're a socks proxy.
6259 - Dump a new router.desc on hup, to help confused people who change
6260 their exit policies and then wonder why router.desc doesn't reflect
6262 - Clean up the generic tor.sh init script that we ship with.
6264 - If the exit stream is pending on the resolve, and a destroy arrives,
6265 then the stream wasn't getting removed from the pending list. I
6266 think this was the one causing recent server crashes.
6267 - Use a more robust poll on OSX 10.3, since their poll is flaky.
6268 - When it couldn't resolve any dirservers, it was useless from then on.
6269 Now it reloads the RouterFile (or default dirservers) if it has no
6271 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
6272 many users don't even *have* a /usr/local/sbin/.
6275 Changes in version 0.0.2pre21 - 2004-02-18
6277 - There's a ChangeLog file that actually reflects the changelog.
6278 - There's a 'torify' wrapper script, with an accompanying
6279 tor-tsocks.conf, that simplifies the process of using tsocks for
6280 tor. It even has a man page.
6281 - The tor binary gets installed to sbin rather than bin now.
6282 - Retry streams where the connected cell hasn't arrived in 15 seconds
6283 - Clean up exit policy handling -- get the default out of the torrc,
6284 so we can update it without forcing each server operator to fix
6286 - Allow imaps and pop3s in default exit policy
6288 - Prevent picking middleman nodes as the last node in the circuit
6291 Changes in version 0.0.2pre20 - 2004-01-30
6293 - We now have a deb package, and it's in debian unstable. Go to
6295 - I've split the TotalBandwidth option into BandwidthRate (how many
6296 bytes per second you want to allow, long-term) and
6297 BandwidthBurst (how many bytes you will allow at once before the cap
6298 kicks in). This better token bucket approach lets you, say, set
6299 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
6300 performance while not exceeding your monthly bandwidth quota.
6301 - Push out a tls record's worth of data once you've got it, rather
6302 than waiting until you've read everything waiting to be read. This
6303 may improve performance by pipelining better. We'll see.
6304 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
6305 from failed circuits (if they haven't been connected yet) and attach
6307 - Expire old streams that haven't managed to connect. Some day we'll
6308 have them reattach to new circuits instead.
6311 - Fix several memory leaks that were causing servers to become bloated
6313 - Fix a few very rare assert triggers. A few more remain.
6314 - Setuid to User _before_ complaining about running as root.
6317 Changes in version 0.0.2pre19 - 2004-01-07
6319 - Fix deadlock condition in dns farm. We were telling a child to die by
6320 closing the parent's file descriptor to him. But newer children were
6321 inheriting the open file descriptor from the parent, and since they
6322 weren't closing it, the socket never closed, so the child never read
6323 eof, so he never knew to exit. Similarly, dns workers were holding
6324 open other sockets, leading to all sorts of chaos.
6325 - New cleaner daemon() code for forking and backgrounding.
6326 - If you log to a file, it now prints an entry at the top of the
6327 logfile so you know it's working.
6328 - The onionskin challenge length was 30 bytes longer than necessary.
6329 - Started to patch up the spec so it's not quite so out of date.
6332 Changes in version 0.0.2pre18 - 2004-01-02
6334 - Fix endian issues with the 'integrity' field in the relay header.
6335 - Fix a potential bug where connections in state
6336 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
6339 Changes in version 0.0.2pre17 - 2003-12-30
6341 - Made --debuglogfile (or any second log file, actually) work.
6342 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
6343 adversary could force us into an infinite loop.
6346 - Each onionskin handshake now includes a hash of the computed key,
6347 to prove the server's identity and help perfect forward secrecy.
6348 - Changed cell size from 256 to 512 bytes (working toward compatibility
6350 - Changed cell length to 2 bytes, and moved it to the relay header.
6351 - Implemented end-to-end integrity checking for the payloads of
6353 - Separated streamid from 'recognized' (otherwise circuits will get
6354 messed up when we try to have streams exit from the middle). We
6355 use the integrity-checking to confirm that a cell is addressed to
6357 - Randomize the initial circid and streamid values, so an adversary who
6358 breaks into a node can't learn how many circuits or streams have
6362 Changes in version 0.0.2pre16 - 2003-12-14
6364 - Fixed a bug that made HUP trigger an assert
6365 - Fixed a bug where a circuit that immediately failed wasn't being
6366 counted as a failed circuit in counting retries.
6369 - Now we close the circuit when we get a truncated cell: otherwise we're
6370 open to an anonymity attack where a bad node in the path truncates
6371 the circuit and then we open streams at him.
6372 - Add port ranges to exit policies
6373 - Add a conservative default exit policy
6374 - Warn if you're running tor as root
6375 - on HUP, retry OR connections and close/rebind listeners
6376 - options.EntryNodes: try these nodes first when picking the first node
6377 - options.ExitNodes: if your best choices happen to include any of
6378 your preferred exit nodes, you choose among just those preferred
6380 - options.ExcludedNodes: nodes that are never picked in path building
6383 Changes in version 0.0.2pre15 - 2003-12-03
6384 o Robustness and bugfixes:
6385 - Sometimes clients would cache incorrect DNS resolves, which would
6386 really screw things up.
6387 - An OP that goes offline would slowly leak all its sockets and stop
6389 - A wide variety of bugfixes in exit node selection, exit policy
6390 handling, and processing pending streams when a new circuit is
6392 - Pick nodes for a path only from those the directory says are up
6393 - Choose randomly from all running dirservers, not always the first one
6394 - Increase allowed http header size for directory fetch.
6395 - Stop writing to stderr (if we're daemonized it will be closed).
6396 - Enable -g always, so cores will be more useful to me.
6397 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
6400 - Wrote a man page. It lists commonly used options.
6403 - Change default loglevel to warn.
6404 - Make PidFile default to null rather than littering in your CWD.
6405 - OnionRouter config option is now obsolete. Instead it just checks
6407 - Moved to a single unified torrc file for both clients and servers.
6410 Changes in version 0.0.2pre14 - 2003-11-29
6411 o Robustness and bugfixes:
6412 - Force the admin to make the DataDirectory himself
6413 - to get ownership/permissions right
6414 - so clients no longer make a DataDirectory and then never use it
6415 - fix bug where a client who was offline for 45 minutes would never
6416 pull down a directory again
6417 - fix (or at least hide really well) the dns assert bug that was
6418 causing server crashes
6419 - warnings and improved robustness wrt clockskew for certs
6420 - use the native daemon(3) to daemonize, when available
6421 - exit if bind() fails
6422 - exit if neither socksport nor orport is defined
6423 - include our own tor_timegm (Win32 doesn't have its own)
6424 - bugfix for win32 with lots of connections
6425 - fix minor bias in PRNG
6426 - make dirserver more robust to corrupt cached directory
6429 - Wrote the design document (woo)
6431 o Circuit building and exit policies:
6432 - Circuits no longer try to use nodes that the directory has told them
6434 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
6435 bitcounts (18.0.0.0/8).
6436 - Make AP connections standby for a circuit if no suitable circuit
6437 exists, rather than failing
6438 - Circuits choose exit node based on addr/port, exit policies, and
6439 which AP connections are standing by
6440 - Bump min pathlen from 2 to 3
6441 - Relay end cells have a payload to describe why the stream ended.
6442 - If the stream failed because of exit policy, try again with a new
6444 - Clients have a dns cache to remember resolved addresses.
6445 - Notice more quickly when we have no working circuits
6448 - APPort is now called SocksPort
6449 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
6451 - RecommendedVersions is now a config variable rather than
6452 hardcoded (for dirservers)
6453 - Reloads config on HUP
6454 - Usage info on -h or --help
6455 - If you set User and Group config vars, it'll setu/gid to them.
6457 Changes in version 0.0.2pre13 - 2003-10-19
6458 o General stability:
6459 - SSL_write no longer fails when it returns WANTWRITE and the number
6460 of bytes in the buf has changed by the next SSL_write call.
6461 - Fix segfault fetching directory when network is down
6462 - Fix a variety of minor memory leaks
6463 - Dirservers reload the fingerprints file on HUP, so I don't have
6464 to take down the network when I approve a new router
6465 - Default server config file has explicit Address line to specify fqdn
6468 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
6469 - Make listener connections not ever alloc bufs
6471 o Autoconf improvements:
6472 - don't clobber an external CFLAGS in ./configure
6473 - Make install now works
6474 - create var/lib/tor on make install
6475 - autocreate a tor.sh initscript to help distribs
6476 - autocreate the torrc and sample-server-torrc with correct paths
6478 o Log files and Daemonizing now work:
6479 - If --DebugLogFile is specified, log to it at -l debug
6480 - If --LogFile is specified, use it instead of commandline
6481 - If --RunAsDaemon is set, tor forks and backgrounds on startup