ChangeLog 420 KB
Newer Older
1
Changes in version 0.2.2.3-alpha - 2009-09-23
2
3
  o Major bugfixes:
    - Fix an overzealous assert in our new circuit build timeout code.
4
      Bugfix on 0.2.2.2-alpha; fixes bug 1103.
5

6
7
8
  o Minor bugfixes:
    - If the networkstatus consensus tells us that we should use a
      negative circuit package window, ignore it. Otherwise we'll
9
      believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
10

11

Roger Dingledine's avatar
Roger Dingledine committed
12
Changes in version 0.2.2.2-alpha - 2009-09-21
13
  o Major features:
14
15
16
17
18
19
20
21
22
23
24
25
    - Tor now tracks how long it takes to build client-side circuits
      over time, and adapts its timeout to local network performance.
      Since a circuit that takes a long time to build will also provide
      bad performance, we get significant latency improvements by
      discarding the slowest 20% of circuits. Specifically, Tor creates
      circuits more aggressively than usual until it has enough data
      points for a good timeout estimate. Implements proposal 151.
      We are especially looking for reports (good and bad) from users with
      both EDGE and broadband connections that can move from broadband
      to EDGE and find out if the build-time data in the .tor/state gets
      reset without loss of Tor usability. You should also see a notice
      log message telling you that Tor has reset its timeout.
26
27
28
    - Directory authorities can now vote on arbitary integer values as
      part of the consensus process. This is designed to help set
      network-wide parameters. Implements proposal 167.
29
30
31
    - Tor now reads the "circwindow" parameter out of the consensus,
      and uses that value for its circuit package window rather than the
      default of 1000 cells. Begins the implementation of proposal 168.
32

33
34
35
36
37
  o Major bugfixes:
    - Fix a remotely triggerable memory leak when a consensus document
      contains more than one signature from the same voter. Bugfix on
      0.2.0.3-alpha.

38
39
40
41
  o Minor bugfixes:
    - Fix an extremely rare infinite recursion bug that could occur if
      we tried to log a message after shutting down the log subsystem.
      Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
42
    - Fix parsing for memory or time units given without a space between
43
      the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
44
45
    - A networkstatus vote must contain exactly one signature. Spec
      conformance issue. Bugfix on 0.2.0.3-alpha.
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
    - Fix an obscure bug where hidden services on 64-bit big-endian
      systems might mis-read the timestamp in v3 introduce cells, and
      refuse to connect back to the client. Discovered by "rotor".
      Bugfix on 0.2.1.6-alpha.
    - We were triggering a CLOCK_SKEW controller status event whenever
      we connect via the v2 connection protocol to any relay that has
      a wrong clock. Instead, we should only inform the controller when
      it's a trusted authority that claims our clock is wrong. Bugfix
      on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
    - We were telling the controller about CHECKING_REACHABILITY and
      REACHABILITY_FAILED status events whenever we launch a testing
      circuit or notice that one has failed. Instead, only tell the
      controller when we want to inform the user of overall success or
      overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
      by SwissTorExit.
    - Don't warn when we're using a circuit that ends with a node
      excluded in ExcludeExitNodes, but the circuit is not used to access
Roger Dingledine's avatar
Roger Dingledine committed
63
64
      the outside world. This should help fix bug 1090, but more problems
      remain. Bugfix on 0.2.1.6-alpha.
65
66
67
    - Work around a small memory leak in some versions of OpenSSL that
      stopped the memory used by the hostname TLS extension from being
      freed.
68
69
70
    - Make our 'torify' script more portable; if we have only one of
      'torsocks' or 'tsocks' installed, don't complain to the user;
      and explain our warning about tsocks better.
71
72
73
74
75
76
77

  o Minor features:
    - Add a "getinfo status/accepted-server-descriptor" controller
      command, which is the recommended way for controllers to learn
      whether our server descriptor has been successfully received by at
      least on directory authority. Un-recommend good-server-descriptor
      getinfo and status events until we have a better design for them.
78
    - Update to the "September 4 2009" ip-to-country file.
79
80


81
Changes in version 0.2.2.1-alpha - 2009-08-26
82
83
84
85
86
87
  o Security fixes:
    - Start the process of disabling ".exit" address notation, since it
      can be used for a variety of esoteric application-level attacks
      on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
      on 0.0.9rc5.

88
89
90
91
  o New directory authorities:
    - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
      authority.

92
  o Major features:
93
94
95
96
97
98
99
100
101
102
103
104
105
    - New AccelName and AccelDir options add support for dynamic OpenSSL
      hardware crypto acceleration engines.
    - Tor now supports tunneling all of its outgoing connections over
      a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
      configuration options. Code by Christopher Davis.

  o Major bugfixes:
    - Send circuit or stream sendme cells when our window has decreased
      by 100 cells, not when it has decreased by 101 cells. Bug uncovered
      by Karsten when testing the "reduce circuit window" performance
      patch. Bugfix on the 54th commit on Tor -- from July 2002,
      before the release of Tor 0.0.0. This is the new winner of the
      oldest-bug prize.
106

107
  o New options for gathering stats safely:
108
109
110
111
112
113
114
    - Directories that set "DirReqStatistics 1" write statistics on
      directory request to disk every 24 hours. As compared to the
      --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
      1) stats are written to disk exactly every 24 hours; 2) estimated
      shares of v2 and v3 requests are determined as mean values, not at
      the end of a measurement period; 3) unresolved requests are listed
      with country code '??'; 4) directories also measure download times.
115
116
117
    - Exit nodes that set "ExitPortStatistics 1" write statistics on the
      number of exit streams and transferred bytes per port to disk every
      24 hours.
118
119
120
121
122
    - Relays that set "CellStatistics 1" write statistics on how long
      cells spend in their circuit queues to disk every 24 hours.
    - Entry nodes that set "EntryStatistics 1" write statistics on the
      rough number and origins of connecting clients to disk every 24
      hours.
123
124
125
    - Relays that write any of the above statistics to disk and set
      "ExtraInfoStatistics 1" include the past 24 hours of statistics in
      their extra-info documents.
126

127
  o Minor features:
128
129
    - New --digests command-line switch to output the digests of the
      source files Tor was built with.
130
    - The "torify" script now uses torsocks where available.
131
    - The memarea code now uses a sentinel value at the end of each area
132
      to make sure nothing writes beyond the end of an area. This might
133
      help debug some conceivable causes of bug 930.
134
    - Time and memory units in the configuration file can now be set to
135
      fractional units. For example, "2.5 GB" is now a valid value for
136
      AccountingMax.
137
138
139
140
141
142
    - Certain Tor clients (such as those behind check.torproject.org) may
      want to fetch the consensus in an extra early manner. To enable this
      a user may now set FetchDirInfoExtraEarly to 1. This also depends on
      setting FetchDirInfoEarly to 1. Previous behavior will stay the same
      as only certain clients who must have this information sooner should
      set this option.
143
144
    - Instead of adding the svn revision to the Tor version string, report
      the git commit (when we're building from a git checkout).
145

146
147
148
149
  o Minor bugfixes:
    - If any the v3 certs we download are unparseable, we should actually
      notice the failure so we don't retry indefinitely. Bugfix on
      0.2.0.x; reported by "rotator".
150
    - If the cached cert file is unparseable, warn but don't exit.
151
152
    - Fix possible segmentation fault on directory authorities. Bugfix on
      0.2.1.14-rc.
153
154
    - When Tor fails to parse a descriptor of any kind, dump it to disk.
      Might help diagnosing bug 1051.
155

156
157
  o Deprecated and removed features:
    - The controller no longer accepts the old obsolete "addr-mappings/"
158
      or "unregistered-servers-" GETINFO values.
Karsten Loesing's avatar
Karsten Loesing committed
159
    - Hidden services no longer publish version 0 descriptors, and clients
160
161
162
      do not request or use version 0 descriptors. However, the old hidden
      service authorities still accept and serve version 0 descriptors
      when contacted by older hidden services/clients.
163
164
165
    - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
      always on; using them is necessary for correct forward-compatible
      controllers.
166
167
168
    - Remove support for .noconnect style addresses. Nobody was using
      them, and they provided another avenue for detecting Tor users
      via application-level web tricks.
169

170
  o Packaging changes:
171
172
173
174
175
176
177
    - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
      installer bundles. See
      https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
      for details of what's new in Vidalia 0.2.3.
    - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
    - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
      configuration file, rather than the old Privoxy.
178
    - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
179
      x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
180
181
182
    - OS X Tor Expert Bundle: Tor is compiled as x86-only for
      better compatibility with OS X 10.6, aka Snow Leopard.
    - OS X Vidalia Bundle: The multi-package installer is now replaced
183
184
      by a simple drag and drop to the /Applications folder. This change
      occurred with the upgrade to Vidalia 0.2.3.
185

186

187
Changes in version 0.2.1.20 - 2009-??-??
188
189
190
191
192
193
194
  o Major bugfixes:
    - Send circuit or stream sendme cells when our window has decreased
      by 100 cells, not when it has decreased by 101 cells. Bug uncovered
      by Karsten when testing the "reduce circuit window" performance
      patch. Bugfix on the 54th commit on Tor -- from July 2002,
      before the release of Tor 0.0.0. This is the new winner of the
      oldest-bug prize.
195
196
197
    - Fix a remotely triggerable memory leak when a consensus document
      contains more than one signature from the same voter. Bugfix on
      0.2.0.3-alpha.
198

199
200
201
202
  o New directory authorities:
    - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
      authority.

203
204
  o Minor bugfixes:
    - Fix a signed/unsigned compile warning in 0.2.1.19.
205
206
    - Fix possible segmentation fault on directory authorities. Bugfix on
      0.2.1.14-rc.
207
208
209
    - Fix an extremely rare infinite recursion bug that could occur if
      we tried to log a message after shutting down the log subsystem.
      Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
210
211
212
213
    - Fix an obscure bug where hidden services on 64-bit big-endian
      systems might mis-read the timestamp in v3 introduce cells, and
      refuse to connect back to the client. Discovered by "rotor".
      Bugfix on 0.2.1.6-alpha.
214
215
216
217
218
    - We were triggering a CLOCK_SKEW controller status event whenever
      we connect via the v2 connection protocol to any relay that has
      a wrong clock. Instead, we should only inform the controller when
      it's a trusted authority that claims our clock is wrong. Bugfix
      on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
219
220
221
222
223
224
    - We were telling the controller about CHECKING_REACHABILITY and
      REACHABILITY_FAILED status events whenever we launch a testing
      circuit or notice that one has failed. Instead, only tell the
      controller when we want to inform the user of overall success or
      overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
      by SwissTorExit.
225
226
227
228
    - Don't warn when we're using a circuit that ends with a node
      excluded in ExcludeExitNodes, but the circuit is not used to access
      the outside world. This should help fix bug 1090. Bugfix on
      0.2.1.6-alpha.
229
230
231
    - Avoid segfault in rare cases when finishing an introduction circuit
      as a client and finding out that we don't have an introduction key
      for it. Fixes bug 1073. Reported by Aaron Swartz.
232
233
234
    - Work around a small memory leak in some versions of OpenSSL that
      stopped the memory used by the hostname TLS extension from being
      freed.
235

236
237
238
239
240
241
242
  o Minor features:
    - Add a "getinfo status/accepted-server-descriptor" controller
      command, which is the recommended way for controllers to learn
      whether our server descriptor has been successfully received by at
      least on directory authority. Un-recommend good-server-descriptor
      getinfo and status events until we have a better design for them.

243

Roger Dingledine's avatar
Roger Dingledine committed
244
Changes in version 0.2.1.19 - 2009-07-28
245
246
247
  Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
  services on Tor 0.2.1.3-alpha through 0.2.1.18.

248
  o Major bugfixes:
249
250
251
    - Make accessing hidden services on 0.2.1.x work right again.
      Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
      part of patch provided by "optimist".
252

253
254
255
256
257
258
  o Minor features:
    - When a relay/bridge is writing out its identity key fingerprint to
      the "fingerprint" file and to its logs, write it without spaces. Now
      it will look like the fingerprints in our bridges documentation,
      and confuse fewer users.

259
  o Minor bugfixes:
260
261
262
263
    - Relays no longer publish a new server descriptor if they change
      their MaxAdvertisedBandwidth config option but it doesn't end up
      changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
      fixes bug 1026. Patch from Sebastian.
264
265
266
267
    - Avoid leaking memory every time we get a create cell but we have
      so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
      fixes bug 1034. Reported by BarkerJr.

268

269
Changes in version 0.2.1.18 - 2009-07-24
270
271
272
273
274
275
  Tor 0.2.1.18 lays the foundations for performance improvements,
  adds status events to help users diagnose bootstrap problems, adds
  optional authentication/authorization for hidden services, fixes a
  variety of potential anonymity problems, and includes a huge pile of
  other features and bug fixes.

276
277
278
279
  o Build fixes:
    - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.


280
Changes in version 0.2.1.17-rc - 2009-07-07
281
282
283
284
285
286
287
288
289
290
291
  Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
  candidate for the 0.2.1.x series. It lays the groundwork for further
  client performance improvements, and also fixes a big bug with directory
  authorities that were causing them to assign Guard and Stable flags
  poorly.

  The Windows bundles also finally include the geoip database that we
  thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
  should actually install Torbutton rather than giving you a cryptic
  failure message (oops).

292
293
294
295
296
297
298
  o Major features:
    - Clients now use the bandwidth values in the consensus, rather than
      the bandwidth values in each relay descriptor. This approach opens
      the door to more accurate bandwidth estimates once the directory
      authorities start doing active measurements. Implements more of
      proposal 141.

299
  o Major bugfixes:
300
301
302
303
304
305
306
    - When Tor clients restart after 1-5 days, they discard all their
      cached descriptors as too old, but they still use the cached
      consensus document. This approach is good for robustness, but
      bad for performance: since they don't know any bandwidths, they
      end up choosing at random rather than weighting their choice by
      speed. Fixed by the above feature of putting bandwidths in the
      consensus. Bugfix on 0.2.0.x.
307
308
309
310
311
312
313
314
315
    - Directory authorities were neglecting to mark relays down in their
      internal histories if the relays fall off the routerlist without
      ever being found unreachable. So there were relays in the histories
      that haven't been seen for eight months, and are listed as being
      up for eight months. This wreaked havoc on the "median wfu"
      and "median mtbf" calculations, in turn making Guard and Stable
      flags very wrong, hurting network performance. Fixes bugs 696 and
      969. Bugfix on 0.2.0.6-alpha.

316
317
  o Minor bugfixes:
    - Serve the DirPortFrontPage page even when we have been approaching
318
319
320
321
322
323
324
325
      our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
    - The control port would close the connection before flushing long
      replies, such as the network consensus, if a QUIT command was issued
      before the reply had completed. Now, the control port flushes all
      pending replies before closing the connection. Also fixed a spurious
      warning when a QUIT command is issued after a malformed or rejected
      AUTHENTICATE command, but before the connection was closed. Patch
      by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
326
327
    - When we can't find an intro key for a v2 hidden service descriptor,
      fall back to the v0 hidden service descriptor and log a bug message.
328
      Workaround for bug 1024.
329
330
    - Fix a log message that did not respect the SafeLogging option.
      Resolves bug 1027.
331

332
333
334
335
  o Minor features:
    - If we're a relay and we change our IP address, be more verbose
      about the reason that made us change. Should help track down
      further bugs for relays on dynamic IP addresses.
336

337

338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
Changes in version 0.2.0.35 - 2009-06-24
  o Security fix:
    - Avoid crashing in the presence of certain malformed descriptors.
      Found by lark, and by automated fuzzing.
    - Fix an edge case where a malicious exit relay could convince a
      controller that the client's DNS question resolves to an internal IP
      address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.

  o Major bugfixes:
    - Finally fix the bug where dynamic-IP relays disappear when their
      IP address changes: directory mirrors were mistakenly telling
      them their old address if they asked via begin_dir, so they
      never got an accurate answer about their new address, so they
      just vanished after a day. For belt-and-suspenders, relays that
      don't set Address in their config now avoid using begin_dir for
      all direct connections. Should fix bugs 827, 883, and 900.
    - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
      that would occur on some exit nodes when DNS failures and timeouts
      occurred in certain patterns. Fix for bug 957.

  o Minor bugfixes:
    - When starting with a cache over a few days old, do not leak
      memory for the obsolete router descriptors in it. Bugfix on
      0.2.0.33; fixes bug 672.
    - Hidden service clients didn't use a cached service descriptor that
      was older than 15 minutes, but wouldn't fetch a new one either,
      because there was already one in the cache. Now, fetch a v2
      descriptor unless the same descriptor was added to the cache within
      the last 15 minutes. Fixes bug 997; reported by Marcus Griep.


Nick Mathewson's avatar
Nick Mathewson committed
369
Changes in version 0.2.1.16-rc - 2009-06-20
370
371
372
  Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
  a bunch of minor bugs.

373
374
375
376
377
  o Security fixes:
    - Fix an edge case where a malicious exit relay could convince a
      controller that the client's DNS question resolves to an internal IP
      address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.

378
379
  o Major performance improvements (on 0.2.0.x):
    - Disable and refactor some debugging checks that forced a linear scan
380
381
382
      over the whole server-side DNS cache. These accounted for over 50%
      of CPU time on a relatively busy exit node's gprof profile. Found
      by Jacob.
383
384
385
    - Disable some debugging checks that appeared in exit node profile
      data.

386
387
  o Minor features:
    - Update to the "June 3 2009" ip-to-country file.
388
    - Do not have tor-resolve automatically refuse all .onion addresses;
389
      if AutomapHostsOnResolve is set in your torrc, this will work fine.
390

391
392
393
  o Minor bugfixes (on 0.2.0.x):
    - Log correct error messages for DNS-related network errors on
      Windows.
394
395
396
    - Fix a race condition that could cause crashes or memory corruption
      when running as a server with a controller listening for log
      messages.
397
    - Avoid crashing when we have a policy specified in a DirPolicy or
398
399
      SocksPolicy or ReachableAddresses option with ports set on it,
      and we re-load the policy. May fix bug 996.
Karsten Loesing's avatar
Karsten Loesing committed
400
401
402
403
404
    - Hidden service clients didn't use a cached service descriptor that
      was older than 15 minutes, but wouldn't fetch a new one either,
      because there was already one in the cache. Now, fetch a v2
      descriptor unless the same descriptor was added to the cache within
      the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
405

406
  o Minor bugfixes (on 0.2.1.x):
407
408
409
    - Don't warn users about low port and hibernation mix when they
      provide a *ListenAddress directive to fix that. Bugfix on
      0.2.1.15-rc.
410
411
    - When switching back and forth between bridge mode, do not start
      gathering GeoIP data until two hours have passed.
412
    - Do not complain that the user has requested an excluded node as
413
      an exit when the node is not really an exit. This could happen
414
415
      because the circuit was for testing, or an introduction point.
      Fix for bug 984.
416

417

418
Changes in version 0.2.1.15-rc - 2009-05-25
419
420
421
422
  Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
  series. It fixes a major bug on fast exit relays, as well as a variety
  of more minor bugs.

423
  o Major bugfixes (on 0.2.0.x):
424
425
    - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
      that would occur on some exit nodes when DNS failures and timeouts
426
      occurred in certain patterns. Fix for bug 957.
427

428
  o Minor bugfixes (on 0.2.0.x):
429
430
431
    - Actually return -1 in the error case for read_bandwidth_usage().
      Harmless bug, since we currently don't care about the return value
      anywhere. Bugfix on 0.2.0.9-alpha.
432
433
    - Provide a more useful log message if bug 977 (related to buffer
      freelists) ever reappears, and do not crash right away.
434
435
436
    - Fix an assertion failure on 64-bit platforms when we allocated
      memory right up to the end of a memarea, then realigned the memory
      one step beyond the end. Fixes a possible cause of bug 930.
437
438
    - Protect the count of open sockets with a mutex, so we can't
      corrupt it when two threads are closing or opening sockets at once.
439
440
441
      Fix for bug 939. Bugfix on 0.2.0.1-alpha.
    - Don't allow a bridge to publish its router descriptor to a
      non-bridge directory authority. Fixes part of bug 932.
442
    - When we change to or from being a bridge, reset our counts of
443
      client usage by country. Fixes bug 932.
444
445
    - Fix a bug that made stream bandwidth get misreported to the
      controller.
446
    - Stop using malloc_usable_size() to use more area than we had
447
      actually allocated: it was safe, but made valgrind really unhappy.
448
449
    - Fix a memory leak when v3 directory authorities load their keys
      and cert from disk. Bugfix on 0.2.0.1-alpha.
450

451
452
453
454
  o Minor bugfixes (on 0.2.1.x):
    - Fix use of freed memory when deciding to mark a non-addable
      descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.

455

456
Changes in version 0.2.1.14-rc - 2009-04-12
Roger Dingledine's avatar
Roger Dingledine committed
457
458
459
460
461
  Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
  series. It begins fixing some major performance problems, and also
  finally addresses the bug that was causing relays on dynamic IP
  addresses to fall out of the directory.

462
463
464
465
466
467
  o Major features:
    - Clients replace entry guards that were chosen more than a few months
      ago. This change should significantly improve client performance,
      especially once more people upgrade, since relays that have been
      a guard for a long time are currently overloaded.

468
469
  o Major bugfixes (on 0.2.0):
    - Finally fix the bug where dynamic-IP relays disappear when their
470
471
472
473
474
475
      IP address changes: directory mirrors were mistakenly telling
      them their old address if they asked via begin_dir, so they
      never got an accurate answer about their new address, so they
      just vanished after a day. For belt-and-suspenders, relays that
      don't set Address in their config now avoid using begin_dir for
      all direct connections. Should fix bugs 827, 883, and 900.
476
    - Relays were falling out of the networkstatus consensus for
477
478
479
480
      part of a day if they changed their local config but the
      authorities discarded their new descriptor as "not sufficiently
      different". Now directory authorities accept a descriptor as changed
      if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
481
      patch by Sebastian.
482
483
    - Avoid crashing in the presence of certain malformed descriptors.
      Found by lark, and by automated fuzzing.
484

485
  o Minor features:
Roger Dingledine's avatar
Roger Dingledine committed
486
487
488
489
    - When generating circuit events with verbose nicknames for
      controllers, try harder to look up nicknames for routers on a
      circuit. (Previously, we would look in the router descriptors we had
      for nicknames, but not in the consensus.) Partial fix for bug 941.
490
491
492
    - If the bridge config line doesn't specify a port, assume 443.
      This makes bridge lines a bit smaller and easier for users to
      understand.
493
494
495
496
497
498
    - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
      bytes (aka 20KB/s), to match our documentation. Also update
      directory authorities so they always assign the Fast flag to relays
      with 20KB/s of capacity. Now people running relays won't suddenly
      find themselves not seeing any use, if the network gets faster
      on average.
499
    - Update to the "April 3 2009" ip-to-country file.
500

Roger Dingledine's avatar
Roger Dingledine committed
501
502
503
504
  o Minor bugfixes:
    - Avoid trying to print raw memory to the logs when we decide to
      give up on downloading a given relay descriptor. Bugfix on
      0.2.1.9-alpha.
505
506
507
    - In tor-resolve, when the Tor client to use is specified by
      <hostname>:<port>, actually use the specified port rather than
      defaulting to 9050. Bugfix on 0.2.1.6-alpha.
508
    - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
509
    - When starting with a cache over a few days old, do not leak
Roger Dingledine's avatar
Roger Dingledine committed
510
      memory for the obsolete router descriptors in it. Bugfix on
511
      0.2.0.33.
512
    - Avoid double-free on list of successfully uploaded hidden
Roger Dingledine's avatar
Roger Dingledine committed
513
      service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
514
    - Change memarea_strndup() implementation to work even when
Roger Dingledine's avatar
Roger Dingledine committed
515
      duplicating a string at the end of a page. This bug was
516
      harmless for now, but could have meant crashes later. Fix by
Roger Dingledine's avatar
Roger Dingledine committed
517
      lark. Bugfix on 0.2.1.1-alpha.
518
519
520
521
    - Limit uploaded directory documents to be 16M rather than 500K.
      The directory authorities were refusing v3 consensus votes from
      other authorities, since the votes are now 504K. Fixes bug 959;
      bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
522
523
524
    - Directory authorities should never send a 503 "busy" response to
      requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
      bug 959.
Roger Dingledine's avatar
Roger Dingledine committed
525
526


Roger Dingledine's avatar
Roger Dingledine committed
527
Changes in version 0.2.1.13-alpha - 2009-03-09
Roger Dingledine's avatar
Roger Dingledine committed
528
529
530
  Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
  cleanups. We're finally getting close to a release candidate.

531
  o Major bugfixes:
532
533
534
    - Correctly update the list of which countries we exclude as
      exits, when the GeoIP file is loaded or reloaded. Diagnosed by
      lark. Bugfix on 0.2.1.6-alpha.
535

536
  o Minor bugfixes (on 0.2.0.x and earlier):
537
538
539
    - Automatically detect MacOSX versions earlier than 10.4.0, and
      disable kqueue from inside Tor when running with these versions.
      We previously did this from the startup script, but that was no
540
      help to people who didn't use the startup script. Resolves bug 863.
541
542
    - When we had picked an exit node for a connection, but marked it as
      "optional", and it turned out we had no onion key for the exit,
543
544
545
      stop wanting that exit and try again. This situation may not
      be possible now, but will probably become feasible with proposal
      158. Spotted by rovv. Fixes another case of bug 752.
546
    - Clients no longer cache certificates for authorities they do not
547
      recognize. Bugfix on 0.2.0.9-alpha.
548
    - When we can't transmit a DNS request due to a network error, retry
549
550
      it after a while, and eventually transmit a failing response to
      the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
551
552
553
554
    - If the controller claimed responsibility for a stream, but that
      stream never finished making its connection, it would live
      forever in circuit_wait state. Now we close it after SocksTimeout
      seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
555
556
557
558
    - Drop begin cells to a hidden service if they come from the middle
      of a circuit. Patch from lark.
    - When we erroneously receive two EXTEND cells for the same circuit
      ID on the same connection, drop the second. Patch from lark.
Nick Mathewson's avatar
Nick Mathewson committed
559
    - Fix a crash that occurs on exit nodes when a nameserver request
560
561
562
      timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
      been suppressing the bug since 0.1.2.10-alpha. Partial fix for
      bug 929.
563
564
    - Do not assume that a stack-allocated character array will be
      64-bit aligned on platforms that demand that uint64_t access is
565
      aligned. Possible fix for bug 604.
566
567
    - Parse dates and IPv4 addresses in a locale- and libc-independent
      manner, to avoid platform-dependent behavior on malformed input.
568
    - Build correctly when configured to build outside the main source
569
      path. Patch from Michael Gold.
570
571
572
    - We were already rejecting relay begin cells with destination port
      of 0. Now also reject extend cells with destination port or address
      of 0. Suggested by lark.
573
574
575
576
577
578

  o Minor bugfixes (on 0.2.1.x):
    - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
      cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
    - If we're an exit node, scrub the IP address to which we are exiting
      in the logs. Bugfix on 0.2.1.8-alpha.
579

580
581
582
  o Minor features:
    - On Linux, use the prctl call to re-enable core dumps when the user
      is option is set.
583
584
585
    - New controller event NEWCONSENSUS that lists the networkstatus
      lines for every recommended relay. Now controllers like Torflow
      can keep up-to-date on which relays they should be using.
586
    - Update to the "February 26 2009" ip-to-country file.
587

588

589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
Changes in version 0.2.0.34 - 2009-02-08
  Tor 0.2.0.34 features several more security-related fixes. You should
  upgrade, especially if you run an exit relay (remote crash) or a
  directory authority (remote infinite loop), or you're on an older
  (pre-XP) or not-recently-patched Windows (remote exploit).

  This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
  have many known flaws, and nobody should be using them. You should
  upgrade. If you're using a Linux or BSD and its packages are obsolete,
  stop using those packages and upgrade anyway.

  o Security fixes:
    - Fix an infinite-loop bug on handling corrupt votes under certain
      circumstances. Bugfix on 0.2.0.8-alpha.
    - Fix a temporary DoS vulnerability that could be performed by
      a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
    - Avoid a potential crash on exit nodes when processing malformed
      input. Remote DoS opportunity. Bugfix on 0.2.0.33.
    - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
      Spec conformance issue. Bugfix on Tor 0.0.2pre27.

  o Minor bugfixes:
    - Fix compilation on systems where time_t is a 64-bit integer.
      Patch from Matthias Drochner.
    - Don't consider expiring already-closed client connections. Fixes
      bug 893. Bugfix on 0.0.2pre20.


617
Changes in version 0.2.1.12-alpha - 2009-02-08
618
619
620
621
622
623
  Tor 0.2.1.12-alpha features several more security-related fixes. You
  should upgrade, especially if you run an exit relay (remote crash) or
  a directory authority (remote infinite loop), or you're on an older
  (pre-XP) or not-recently-patched Windows (remote exploit). It also
  includes a big pile of minor bugfixes and cleanups.

624
  o Security fixes:
625
    - Fix an infinite-loop bug on handling corrupt votes under certain
Roger Dingledine's avatar
Roger Dingledine committed
626
      circumstances. Bugfix on 0.2.0.8-alpha.
Roger Dingledine's avatar
Roger Dingledine committed
627
628
    - Fix a temporary DoS vulnerability that could be performed by
      a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
629
    - Avoid a potential crash on exit nodes when processing malformed
Roger Dingledine's avatar
Roger Dingledine committed
630
      input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
631

632
  o Minor bugfixes:
633
634
635
    - Let controllers actually ask for the "clients_seen" event for
      getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
      reported by Matt Edman.
Roger Dingledine's avatar
Roger Dingledine committed
636
    - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
637
      0.2.1.11-alpha.
638
639
    - Fix a bug in address parsing that was preventing bridges or hidden
      service targets from being at IPv6 addresses.
640
    - Solve a bug that kept hardware crypto acceleration from getting
Roger Dingledine's avatar
Roger Dingledine committed
641
      enabled when accounting was turned on. Fixes bug 907. Bugfix on
642
      0.0.9pre6.
643
    - Remove a bash-ism from configure.in to build properly on non-Linux
Roger Dingledine's avatar
Roger Dingledine committed
644
      platforms. Bugfix on 0.2.1.1-alpha.
645
    - Fix code so authorities _actually_ send back X-Descriptor-Not-New
Roger Dingledine's avatar
Roger Dingledine committed
646
      headers. Bugfix on 0.2.0.10-alpha.
647
648
    - Don't consider expiring already-closed client connections. Fixes
      bug 893. Bugfix on 0.0.2pre20.
649
    - Fix another interesting corner-case of bug 891 spotted by rovv:
Roger Dingledine's avatar
Roger Dingledine committed
650
651
652
653
      Previously, if two hosts had different amounts of clock drift, and
      one of them created a new connection with just the wrong timing,
      the other might decide to deprecate the new connection erroneously.
      Bugfix on 0.1.1.13-alpha.
654
655
    - Resolve a very rare crash bug that could occur when the user forced
      a nameserver reconfiguration during the middle of a nameserver
Roger Dingledine's avatar
Roger Dingledine committed
656
      probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
657
658
    - Support changing value of ServerDNSRandomizeCase during SIGHUP.
      Bugfix on 0.2.1.7-alpha.
659
660
661
    - If we're using bridges and our network goes away, be more willing
      to forgive our bridges and try again when we get an application
      request. Bugfix on 0.2.0.x.
662

663
664
  o Minor features:
    - Support platforms where time_t is 64 bits long. (Congratulations,
Roger Dingledine's avatar
Roger Dingledine committed
665
666
667
      NetBSD!) Patch from Matthias Drochner.
    - Add a 'getinfo status/clients-seen' controller command, in case
      controllers want to hear clients_seen events but connect late.
668

Roger Dingledine's avatar
Roger Dingledine committed
669
  o Build changes:
670
671
672
673
    - Disable GCC's strict alias optimization by default, to avoid the
      likelihood of its introducing subtle bugs whenever our code violates
      the letter of C99's alias rules.

674

675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
Changes in version 0.2.0.33 - 2009-01-21
  Tor 0.2.0.33 fixes a variety of bugs that were making relays less
  useful to users. It also finally fixes a bug where a relay or client
  that's been off for many days would take a long time to bootstrap.

  This update also fixes an important security-related bug reported by
  Ilja van Sprundel. You should upgrade. (We'll send out more details
  about the bug once people have had some time to upgrade.)

  o Security fixes:
    - Fix a heap-corruption bug that may be remotely triggerable on
      some platforms. Reported by Ilja van Sprundel.

  o Major bugfixes:
    - When a stream at an exit relay is in state "resolving" or
      "connecting" and it receives an "end" relay cell, the exit relay
      would silently ignore the end cell and not close the stream. If
      the client never closes the circuit, then the exit relay never
      closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
      reported by "wood".
    - When sending CREATED cells back for a given circuit, use a 64-bit
      connection ID to find the right connection, rather than an addr:port
      combination. Now that we can have multiple OR connections between
      the same ORs, it is no longer possible to use addr:port to uniquely
      identify a connection.
    - Bridge relays that had DirPort set to 0 would stop fetching
      descriptors shortly after startup, and then briefly resume
      after a new bandwidth test and/or after publishing a new bridge
      descriptor. Bridge users that try to bootstrap from them would
      get a recent networkstatus but would get descriptors from up to
      18 hours earlier, meaning most of the descriptors were obsolete
      already. Reported by Tas; bugfix on 0.2.0.13-alpha.
    - Prevent bridge relays from serving their 'extrainfo' document
      to anybody who asks, now that extrainfo docs include potentially
      sensitive aggregated client geoip summaries. Bugfix on
      0.2.0.13-alpha.
    - If the cached networkstatus consensus is more than five days old,
      discard it rather than trying to use it. In theory it could be
      useful because it lists alternate directory mirrors, but in practice
      it just means we spend many minutes trying directory mirrors that
      are long gone from the network. Also discard router descriptors as
      we load them if they are more than five days old, since the onion
      key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.

  o Minor bugfixes:
    - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
      could make gcc generate non-functional binary search code. Bugfix
      on 0.2.0.10-alpha.
    - Build correctly on platforms without socklen_t.
    - Compile without warnings on solaris.
    - Avoid potential crash on internal error during signature collection.
      Fixes bug 864. Patch from rovv.
    - Correct handling of possible malformed authority signing key
      certificates with internal signature types. Fixes bug 880.
      Bugfix on 0.2.0.3-alpha.
    - Fix a hard-to-trigger resource leak when logging credential status.
      CID 349.
    - When we can't initialize DNS because the network is down, do not
      automatically stop Tor from starting. Instead, we retry failed
      dns_init() every 10 minutes, and change the exit policy to reject
      *:* until one succeeds. Fixes bug 691.
    - Use 64 bits instead of 32 bits for connection identifiers used with
      the controller protocol, to greatly reduce risk of identifier reuse.
    - When we're choosing an exit node for a circuit, and we have
      no pending streams, choose a good general exit rather than one that
      supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
    - Fix another case of assuming, when a specific exit is requested,
      that we know more than the user about what hosts it allows.
      Fixes one case of bug 752. Patch from rovv.
    - Clip the MaxCircuitDirtiness config option to a minimum of 10
      seconds. Warn the user if lower values are given in the
      configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
    - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
      user if lower values are given in the configuration. Bugfix on
      0.1.1.17-rc. Patch by Sebastian.
    - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
      the cache because we already had a v0 descriptor with the same ID.
      Bugfix on 0.2.0.18-alpha.
    - Fix a race condition when freeing keys shared between main thread
      and CPU workers that could result in a memory leak. Bugfix on
      0.1.0.1-rc. Fixes bug 889.
    - Send a valid END cell back when a client tries to connect to a
      nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
      840. Patch from rovv.
    - Check which hops rendezvous stream cells are associated with to
      prevent possible guess-the-streamid injection attacks from
      intermediate hops. Fixes another case of bug 446. Based on patch
      from rovv.
    - If a broken client asks a non-exit router to connect somewhere,
      do not even do the DNS lookup before rejecting the connection.
      Fixes another case of bug 619. Patch from rovv.
    - When a relay gets a create cell it can't decrypt (e.g. because it's
      using the wrong onion key), we were dropping it and letting the
      client time out. Now actually answer with a destroy cell. Fixes
      bug 904. Bugfix on 0.0.2pre8.

  o Minor bugfixes (hidden services):
    - Do not throw away existing introduction points on SIGHUP. Bugfix on
      0.0.6pre1. Patch by Karsten. Fixes bug 874.

  o Minor features:
    - Report the case where all signatures in a detached set are rejected
      differently than the case where there is an error handling the
      detached set.
    - When we realize that another process has modified our cached
      descriptors, print out a more useful error message rather than
      triggering an assertion. Fixes bug 885. Patch from Karsten.
    - Implement the 0x20 hack to better resist DNS poisoning: set the
      case on outgoing DNS requests randomly, and reject responses that do
      not match the case correctly. This logic can be disabled with the
      ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
      of servers that do not reliably preserve case in replies. See
      "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
      for more info.
    - Check DNS replies for more matching fields to better resist DNS
      poisoning.
    - Never use OpenSSL compression: it wastes RAM and CPU trying to
      compress cells, which are basically all encrypted, compressed, or
      both.


796
Changes in version 0.2.1.11-alpha - 2009-01-20
797
798
799
800
801
802
  Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
  week it will take a long time to bootstrap again" bug. It also fixes
  an important security-related bug reported by Ilja van Sprundel. You
  should upgrade. (We'll send out more details about the bug once people
  have had some time to upgrade.)

803
804
805
806
  o Security fixes:
    - Fix a heap-corruption bug that may be remotely triggerable on
      some platforms. Reported by Ilja van Sprundel.

807
808
809
810
811
812
813
  o Major bugfixes:
    - Discard router descriptors as we load them if they are more than
      five days old. Otherwise if Tor is off for a long time and then
      starts with cached descriptors, it will try to use the onion
      keys in those obsolete descriptors when building circuits. Bugfix
      on 0.2.0.x. Fixes bug 887.

814
815
  o Minor features:
    - Try to make sure that the version of Libevent we're running with
816
      is binary-compatible with the one we built with. May address bug
817
      897 and others.
818
819
    - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
      for bug 905. Bugfix on 0.2.1.7-alpha.
820
821
    - Add a new --enable-local-appdata configuration switch to change
      the default location of the datadir on win32 from APPDATA to
822
823
      LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
      entirely. Patch from coderman.
824

825
826
  o Minor bugfixes:
    - Make outbound DNS packets respect the OutboundBindAddress setting.
827
828
829
830
831
      Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
    - When our circuit fails at the first hop (e.g. we get a destroy
      cell back), avoid using that OR connection anymore, and also
      tell all the one-hop directory requests waiting for it that they
      should fail. Bugfix on 0.2.1.3-alpha.
832
    - In the torify(1) manpage, mention that tsocks will leak your
833
      DNS requests.
834

835

836
Changes in version 0.2.1.10-alpha - 2009-01-06
837
838
839
840
841
842
843
  Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
  would make the bridge relay not so useful if it had DirPort set to 0,
  and one that could let an attacker learn a little bit of information
  about the bridge's users), and a bug that would cause your Tor relay
  to ignore a circuit create request it can't decrypt (rather than reply
  with an error). It also fixes a wide variety of other bugs.

844
845
846
847
848
849
850
  o Major bugfixes:
    - If the cached networkstatus consensus is more than five days old,
      discard it rather than trying to use it. In theory it could
      be useful because it lists alternate directory mirrors, but in
      practice it just means we spend many minutes trying directory
      mirrors that are long gone from the network. Helps bug 887 a bit;
      bugfix on 0.2.0.x.
851
852
853
854
855
856
857
    - Bridge relays that had DirPort set to 0 would stop fetching
      descriptors shortly after startup, and then briefly resume
      after a new bandwidth test and/or after publishing a new bridge
      descriptor. Bridge users that try to bootstrap from them would
      get a recent networkstatus but would get descriptors from up to
      18 hours earlier, meaning most of the descriptors were obsolete
      already. Reported by Tas; bugfix on 0.2.0.13-alpha.
858
859
    - Prevent bridge relays from serving their 'extrainfo' document
      to anybody who asks, now that extrainfo docs include potentially
860
861
      sensitive aggregated client geoip summaries. Bugfix on
      0.2.0.13-alpha.
862

863
864
865
866
867
  o Minor features:
    - New controller event "clients_seen" to report a geoip-based summary
      of which countries we've seen clients from recently. Now controllers
      like Vidalia can show bridge operators that they're actually making
      a difference.
868
869
    - Build correctly against versions of OpenSSL 0.9.8 or later built
      without support for deprecated functions.
870
    - Update to the "December 19 2008" ip-to-country file.
871

872
  o Minor bugfixes (on 0.2.0.x):
873
    - Authorities now vote for the Stable flag for any router whose
874
      weighted MTBF is at least 5 days, regardless of the mean MTBF.
875
    - Do not remove routers as too old if we do not have any consensus
876
      document. Bugfix on 0.2.0.7-alpha.
877
    - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
878
879
880
      Spec conformance issue. Bugfix on Tor 0.0.2pre27.
    - When an exit relay resolves a stream address to a local IP address,
      do not just keep retrying that same exit relay over and
881
882
      over. Instead, just close the stream. Addresses bug 872. Bugfix
      on 0.2.0.32. Patch from rovv.
883
    - If a hidden service sends us an END cell, do not consider
884
      retrying the connection; just close it. Patch from rovv.
885
886
887
888
    - When we made bridge authorities stop serving bridge descriptors over
      unencrypted links, we also broke DirPort reachability testing for
      bridges. So bridges with a non-zero DirPort were printing spurious
      warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
889
890
    - When a relay gets a create cell it can't decrypt (e.g. because it's
      using the wrong onion key), we were dropping it and letting the
891
892
      client time out. Now actually answer with a destroy cell. Fixes
      bug 904. Bugfix on 0.0.2pre8.
893
894
895
896
897
898
899
900
    - Squeeze 2-5% out of client performance (according to oprofile) by
      improving the implementation of some policy-manipulation functions.

  o Minor bugfixes (on 0.2.1.x):
    - Make get_interface_address() function work properly again; stop
      guessing the wrong parts of our address as our address.
    - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
      send on that circuit. Otherwise we might violate the proposal-110
901
      limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
902
903
904
905
906
907
908
909
910
911
912
913
914
915
      thanks to Karsten.
    - When we're sending non-EXTEND cells to the first hop in a circuit,
      for example to use an encrypted directory connection, we don't need
      to use RELAY_EARLY cells: the first hop knows what kind of cell
      it is, and nobody else can even see the cell type. Conserving
      RELAY_EARLY cells makes it easier to cannibalize circuits like
      this later.
    - Stop logging nameserver addresses in reverse order.
    - If we are retrying a directory download slowly over and over, do
      not automatically give up after the 254th failure. Bugfix on
      0.2.1.9-alpha.
    - Resume reporting accurate "stream end" reasons to the local control
      port. They were lost in the changes for Proposal 148. Bugfix on
      0.2.1.9-alpha.
916

917
  o Deprecated and removed features:
918
919
    - The old "tor --version --version" command, which would print out
      the subversion "Id" of most of the source files, is now removed. It
920
921
922
      turned out to be less useful than we'd expected, and harder to
      maintain.

923
924
  o Code simplifications and refactoring:
    - Change our header file guard macros to be less likely to conflict
925
      with system headers. Adam Langley noticed that we were conflicting
926
      with log.h on Android.
927
928
    - Tool-assisted documentation cleanup. Nearly every function or
      static variable in Tor should have its own documentation now.
929

930

Roger Dingledine's avatar
Roger Dingledine committed
931
Changes in version 0.2.1.9-alpha - 2008-12-25
932
933
  Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.

Roger Dingledine's avatar
Roger Dingledine committed
934
935
936
937
  o New directory authorities:
    - gabelmoo (the authority run by Karsten Loesing) now has a new
      IP address.

938
  o Security fixes:
939
    - Never use a connection with a mismatched address to extend a
940
      circuit, unless that connection is canonical. A canonical
941
942
      connection is one whose address is authenticated by the router's
      identity key, either in a NETINFO cell or in a router descriptor.
Roger Dingledine's avatar
Roger Dingledine committed
943
944
    - Avoid a possible memory corruption bug when receiving hidden service
      descriptors. Bugfix on 0.2.1.6-alpha.
945

946
947
  o Major bugfixes:
    - Fix a logic error that would automatically reject all but the first
948
949
      configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
      part of bug 813/868. Bug spotted by coderman.
950
951
952
953
    - When a stream at an exit relay is in state "resolving" or
      "connecting" and it receives an "end" relay cell, the exit relay
      would silently ignore the end cell and not close the stream. If
      the client never closes the circuit, then the exit relay never
Roger Dingledine's avatar
Roger Dingledine committed
954
      closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
955
      reported by "wood".
Roger Dingledine's avatar
Roger Dingledine committed
956
957
    - When we can't initialize DNS because the network is down, do not
      automatically stop Tor from starting. Instead, retry failed
958
      dns_init() every 10 minutes, and change the exit policy to reject
Roger Dingledine's avatar
Roger Dingledine committed
959
      *:* until one succeeds. Fixes bug 691.
960

961
  o Minor features:
962
963
964
    - Give a better error message when an overzealous init script says
      "sudo -u username tor --user username". Makes Bug 882 easier for
      users to diagnose.
965
966
967
    - When a directory authority gives us a new guess for our IP address,
      log which authority we used. Hopefully this will help us debug
      the recent complaints about bad IP address guesses.
968
    - Detect svn revision properly when we're using git-svn.
969
970
971
    - Try not to open more than one descriptor-downloading connection
      to an authority at once. This should reduce load on directory
      authorities. Fixes bug 366.
972
    - Add cross-certification to newly generated certificates, so that
Roger Dingledine's avatar
Roger Dingledine committed
973
      a signing key is enough information to look up a certificate.
974
      Partial implementation of proposal 157.
975
    - Start serving certificates by <identity digest, signing key digest>
976
      pairs. Partial implementation of proposal 157.
977
978
    - Clients now never report any stream end reason except 'MISC'.
      Implements proposal 148.
979
980
981
    - On platforms with a maximum syslog string length, truncate syslog
      messages to that length ourselves, rather than relying on the
      system to do it for us.
Roger Dingledine's avatar
Roger Dingledine committed
982
    - Optimize out calls to time(NULL) that occur for every IO operation,
Roger Dingledine's avatar
Roger Dingledine committed
983
984
      or for every cell. On systems where time() is a slow syscall,
      this fix will be slightly helpful.
985
    - Exit servers can now answer resolve requests for ip6.arpa addresses.
Roger Dingledine's avatar
Roger Dingledine committed
986
987
988
989
990
991
992
    - When we download a descriptor that we then immediately (as
      a directory authority) reject, do not retry downloading it right
      away. Should save some bandwidth on authorities. Fix for bug
      888. Patch by Sebastian Hahn.
    - When a download gets us zero good descriptors, do not notify
      Tor that new directory information has arrived.
    - Avoid some nasty corner cases in the logic for marking connections
993
994
      as too old or obsolete or noncanonical for circuits.  Partial
      bugfix on bug 891.
995

996
  o Minor features (controller):
997
998
    - New CONSENSUS_ARRIVED event to note when a new consensus has
      been fetched and validated.
999
    - When we realize that another process has modified our cached
Roger Dingledine's avatar
Roger Dingledine committed
1000
1001
      descriptors file, print out a more useful error message rather
      than triggering an assertion. Fixes bug 885. Patch from Karsten.
1002
1003
1004
    - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
      controllers to prevent SIGHUP from reloading the
      configuration. Fixes bug 856.
1005

1006
1007
1008
  o Minor bugfixes:
    - Resume using the correct "REASON=" stream when telling the
      controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
1009
1010
    - When a canonical connection appears later in our internal list
      than a noncanonical one for a given OR ID, always use the
1011
      canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
1012
      Spotted by rovv.
1013
1014
1015
1016
1017
1018
    - Clip the MaxCircuitDirtiness config option to a minimum of 10
      seconds. Warn the user if lower values are given in the
      configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
    - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
      user if lower values are given in the configuration. Bugfix on
      0.1.1.17-rc. Patch by Sebastian.
1019
    - Fix a race condition when freeing keys shared between main thread
Roger Dingledine's avatar
Roger Dingledine committed
1020
1021
      and CPU workers that could result in a memory leak. Bugfix on
      0.1.0.1-rc. Fixes bug 889.
1022

1023
  o Minor bugfixes (hidden services):
Roger Dingledine's avatar
Roger Dingledine committed
1024
1025
1026
    - Do not throw away existing introduction points on SIGHUP (bugfix on
      0.0.6pre1); also, do not stall hidden services because we're
      throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
1027
      by John Brooks. Patch by Karsten. Fixes bug 874.
Roger Dingledine's avatar
Roger Dingledine committed
1028
1029
1030
    - Fix a memory leak when we decline to add a v2 rendezvous
      descriptor to the cache because we already had a v0 descriptor
      with the same ID. Bugfix on 0.2.0.18-alpha.
1031

1032
  o Deprecated and removed features:
1033
1034
1035
1036
    - RedirectExits has been removed. It was deprecated since
      0.2.0.3-alpha.
    - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
      has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
Nick Mathewson's avatar
Nick Mathewson committed
1037
    - Cell pools are now always enabled; --disable-cell-pools is ignored.
1038

1039
1040
  o Code simplifications and refactoring:
    - Rename the confusing or_is_obsolete field to the more appropriate
1041
1042
      is_bad_for_new_circs, and move it to or_connection_t where it
      belongs.
1043
1044
    - Move edge-only flags from connection_t to edge_connection_t: not
      only is this better coding, but on machines of plausible alignment,
1045
      it should save 4-8 bytes per connection_t. "Every little bit helps."
1046
1047
    - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
      for consistency; keep old option working for backward compatibility.
1048
    - Simplify the code for finding connections to use for a circuit.
1049

1050

1051
Changes in version 0.2.1.8-alpha - 2008-12-08
1052
1053
1054
1055
  Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
  builds better on unusual platforms like Solaris and old OS X, and
  fixes a variety of other issues.

Roger Dingledine's avatar
Roger Dingledine committed
1056
1057
1058
1059
1060
  o Major features:
    - New DirPortFrontPage option that takes an html file and publishes
      it as "/" on the DirPort. Now relay operators can provide a
      disclaimer without needing to set up a separate webserver. There's
      a sample disclaimer in contrib/tor-exit-notice.html.
1061

1062
1063
1064
1065
1066
1067
  o Security fixes:
    - When the client is choosing entry guards, now it selects at most
      one guard from a given relay family. Otherwise we could end up with
      all of our entry points into the network run by the same operator.
      Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.

1068
1069
1070
  o Major bugfixes:
    - Fix a DOS opportunity during the voting signature collection process
      at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
1071
1072
    - Fix a possible segfault when establishing an exit connection. Bugfix
      on 0.2.1.5-alpha.
1073

1074
  o Minor bugfixes:
1075
    - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
1076
      bug 859.
1077
1078
    - Made Tor a little less aggressive about deleting expired
      certificates. Partial fix for bug 854.
1079
    - Stop doing unaligned memory access that generated bus errors on
1080
1081
1082
1083
      sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
    - Fix a crash bug when changing EntryNodes from the controller. Bugfix
      on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
    - Make USR2 log-level switch take effect immediately. Bugfix on
1084
      0.1.2.8-beta.
1085
1086
    - If one win32 nameserver fails to get added, continue adding the
      rest, and don't automatically fail.
1087
1088
1089
    - Use fcntl() for locking when flock() is not available. Should fix
      compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
    - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
1090
1091
      could make gcc generate non-functional binary search code. Bugfix
      on 0.2.0.10-alpha.
1092
    - Build correctly on platforms without socklen_t.
1093
    - Avoid potential crash on internal error during signature collection.
1094
1095
1096
1097
      Fixes bug 864. Patch from rovv.
    - Do not use C's stdio library for writing to log files. This will
      improve logging performance by a minute amount, and will stop
      leaking fds when our disk is full. Fixes bug 861.
1098
1099
    - Stop erroneous use of O_APPEND in cases where we did not in fact
      want to re-seek to the end of a file before every last write().
1100
    - Correct handling of possible malformed authority signing key
1101
1102
      certificates with internal signature types. Fixes bug 880. Bugfix
      on 0.2.0.3-alpha.
1103
1104
    - Fix a hard-to-trigger resource leak when logging credential status.
      CID 349.
1105
1106

  o Minor features:
1107
1108
1109
    - Directory mirrors no longer fetch the v1 directory or
      running-routers files. They are obsolete, and nobody asks for them
      anymore. This is the first step to making v1 authorities obsolete.
1110

1111
  o Minor features (controller):
1112
    - Return circuit purposes in response to GETINFO circuit-status. Fixes
1113
      bug 858.
1114

Roger Dingledine's avatar
Roger Dingledine committed
1115
1116

Changes in version 0.2.0.32 - 2008-11-20
1117
1118
1119
1120
1121
1122
  Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
  packages (and maybe other packages) noticed by Theo de Raadt, fixes
  a smaller security flaw that might allow an attacker to access local
  services, further improves hidden service performance, and fixes a
  variety of other issues.

Roger Dingledine's avatar
Roger Dingledine committed
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
  o Security fixes:
    - The "User" and "Group" config options did not clear the
      supplementary group entries for the Tor process. The "User" option
      is now more robust, and we now set the groups to the specified
      user's primary group. The "Group" option is now ignored. For more
      detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
      in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
      and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
    - The "ClientDNSRejectInternalAddresses" config option wasn't being
      consistently obeyed: if an exit relay refuses a stream because its
      exit policy doesn't allow it, we would remember what IP address
      the relay said the destination address resolves to, even if it's
      an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.

  o Major bugfixes:
    - Fix a DOS opportunity during the voting signature collection process
      at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.

  o Major bugfixes (hidden services):
    - When fetching v0 and v2 rendezvous service descriptors in parallel,
      we were failing the whole hidden service request when the v0
      descriptor fetch fails, even if the v2 fetch is still pending and
      might succeed. Similarly, if the last v2 fetch fails, we were
      failing the whole hidden service request even if a v0 fetch is
      still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
    - When extending a circuit to a hidden service directory to upload a
      rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
      requests failed, because the router descriptor has not been
      downloaded yet. In these cases, do not attempt to upload the
      rendezvous descriptor, but wait until the router descriptor is
      downloaded and retry. Likewise, do not attempt to fetch a rendezvous
      descriptor from a hidden service directory for which the router
      descriptor has not yet been downloaded. Fixes bug 767. Bugfix
      on 0.2.0.10-alpha.

  o Minor bugfixes:
    - Fix several infrequent memory leaks spotted by Coverity.
    - When testing for libevent functions, set the LDFLAGS variable
      correctly. Found by Riastradh.
    - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
      bootstrapping with tunneled directory connections. Bugfix on
      0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
    - When asked to connect to A.B.exit:80, if we don't know the IP for A
      and we know that server B rejects most-but-not all connections to
      port 80, we would previously reject the connection. Now, we assume
      the user knows what they were asking for. Fixes bug 752. Bugfix
      on 0.0.9rc5. Diagnosed by BarkerJr.
    - If we overrun our per-second write limits a little, count this as
      having used up our write allocation for the second, and choke
      outgoing directory writes. Previously, we had only counted this when
      we had met our limits precisely. Fixes bug 824. Patch from by rovv.
      Bugfix on 0.2.0.x (??).
    - Remove the old v2 directory authority 'lefkada' from the default
      list. It has been gone for many months.
    - Stop doing unaligned memory access that generated bus errors on
      sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
    - Make USR2 log-level switch take effect immediately. Bugfix on
      0.1.2.8-beta.

  o Minor bugfixes (controller):
    - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
      0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.


Roger Dingledine's avatar
Roger Dingledine committed
1187
Changes in version 0.2.1.7-alpha - 2008-11-08
1188
1189
1190
1191
1192
1193
1194
  Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
  packages (and maybe other packages) noticed by Theo de Raadt, fixes
  a smaller security flaw that might allow an attacker to access local
  services, adds better defense against DNS poisoning attacks on exit
  relays, further improves hidden service performance, and fixes a
  variety of other issues.

Roger Dingledine's avatar
Roger Dingledine committed
1195
1196
1197
1198
1199
1200
  o Security fixes:
    - The "ClientDNSRejectInternalAddresses" config option wasn't being
      consistently obeyed: if an exit relay refuses a stream because its
      exit policy doesn't allow it, we would remember what IP address
      the relay said the destination address resolves to, even if it's
      an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
1201
    - The "User" and "Group" config options did not clear the
1202
1203
1204
1205
1206
      supplementary group entries for the Tor process. The "User" option
      is now more robust, and we now set the groups to the specified
      user's primary group. The "Group" option is now ignored. For more
      detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
      in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
Roger Dingledine's avatar
Roger Dingledine committed
1207
1208
1209
      and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
    - Do not use or believe expired v3 authority certificates. Patch
      from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
Roger Dingledine's avatar
Roger Dingledine committed
1210

1211
1212
1213
1214
  o Minor features:
    - Now NodeFamily and MyFamily config options allow spaces in
      identity fingerprints, so it's easier to paste them in.
      Suggested by Lucky Green.
1215
1216
1217
    - Implement the 0x20 hack to better resist DNS poisoning: set the
      case on outgoing DNS requests randomly, and reject responses that do
      not match the case correctly. This logic can be disabled with the
1218
      ServerDNSRandomizeCase setting, if you are using one of the 0.3%
1219
1220
1221
      of servers that do not reliably preserve case in replies. See
      "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
      for more info.
1222
1223
    - Preserve case in replies to DNSPort requests in order to support
      the 0x20 hack for resisting DNS poisoning attacks.
Roger Dingledine's avatar
Roger Dingledine committed
1224
1225

  o Hidden service performance improvements:
1226
1227
    - When the client launches an introduction circuit, retry with a
      new circuit after 30 seconds rather than 60 seconds.
1228
1229
    - Launch a second client-side introduction circuit in parallel
      after a delay of 15 seconds (based on work by Christian Wilms).
Roger Dingledine's avatar
Roger Dingledine committed
1230
1231
1232
1233
    - Hidden services start out building five intro circuits rather
      than three, and when the first three finish they publish a service
      descriptor using those. Now we publish our service descriptor much
      faster after restart.
1234

1235
1236
1237
1238
  o Minor bugfixes:
    - Minor fix in the warning messages when you're having problems
      bootstrapping; also, be more forgiving of bootstrap problems when
      we're still making incremental progress on a given bootstrap phase.
Roger Dingledine's avatar
Roger Dingledine committed
1239
1240
1241
    - When we're choosing an exit node for a circuit, and we have
      no pending streams, choose a good general exit rather than one that
      supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
1242
    - Send a valid END cell back when a client tries to connect to a
1243
1244
      nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
      840. Patch from rovv.
1245
1246
    - If a broken client asks a non-exit router to connect somewhere,
      do not even do the DNS lookup before rejecting the connection.
1247
      Fixes another case of bug 619. Patch from rovv.
1248
1249
    - Fix another case of assuming, when a specific exit is requested,
      that we know more than the user about what hosts it allows.
1250
      Fixes another case of bug 752. Patch from rovv.
1251
1252
    - Check which hops rendezvous stream cells are associated with to
      prevent possible guess-the-streamid injection attacks from
1253
      intermediate hops. Fixes another case of bug 446. Based on patch
1254
      from rovv.
1255