[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[or-cvs] r18811: {tor} declare that i'm going to tag 0.2.1.13-alpha tonight (tor/trunk)



Author: arma
Date: 2009-03-08 20:43:03 -0400 (Sun, 08 Mar 2009)
New Revision: 18811

Modified:
   tor/trunk/ChangeLog
Log:
declare that i'm going to tag 0.2.1.13-alpha tonight


Modified: tor/trunk/ChangeLog
===================================================================
--- tor/trunk/ChangeLog	2009-03-08 23:19:50 UTC (rev 18810)
+++ tor/trunk/ChangeLog	2009-03-09 00:43:03 UTC (rev 18811)
@@ -1,49 +1,50 @@
-Changes in version 0.2.1.13-????? - 2009-02-??
+Changes in version 0.2.1.13-alpha - 2009-02-09
   o Major bugfixes:
-    - Correctly update the list of countries to exclude as exits when
-      the GeoIP file is loaded or reloaded.  Diagnosed by lark.  Bugfix
-      on 0.2.1.6-alpha.
+    - 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.
 
-  o Minor bugfixes:
+  o Minor bugfixes (on 0.2.0.x and earlier):
     - 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
-      help to people who didn't use the startup script.  Resolves
-      bug 863.
+      help to people who didn't use the startup script. Resolves bug 863.
     - 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,
-      stop preferring the 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.
-    - 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.
-    - As an exit node, scrub the IP address to which we are exiting in the
-      logs. Bugfix on 0.2.1.8-alpha.
+      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.
     - Clients no longer cache certificates for authorities they do not
-      recognize.  Bugfix on 0.2.0.9-alpha.
+      recognize. Bugfix on 0.2.0.9-alpha.
     - When we can't transmit a DNS request due to a network error, retry
-      it after a while, and eventually transmit a failing response to the
-      RESOLVED cell.  Bugfix on 0.1.2.5-alpha.
+      it after a while, and eventually transmit a failing response to
+      the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
     - 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.
-    - 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.
+    - 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.
     - Fix a crash that occurs on exit nodes when a nameserver request
-      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.
+      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.
     - Do not assume that a stack-allocated character array will be
       64-bit aligned on platforms that demand that uint64_t access is
-      aligned.  Possible fix for bug 604.
+      aligned. Possible fix for bug 604.
     - Parse dates and IPv4 addresses in a locale- and libc-independent
       manner, to avoid platform-dependent behavior on malformed input.
     - Build correctly when configured to build outside the main source
-      path.  Patch from Michael Gold.
+      path. Patch from Michael Gold.
 
+  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.
+
   o Minor features:
     - On Linux, use the prctl call to re-enable core dumps when the user
       is option is set.
@@ -52,6 +53,7 @@
       can keep up-to-date on which relays they should be using.
     - Update to the "February 26 2009" ip-to-country file.
 
+
 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
@@ -300,6 +302,13 @@
 
 
 Changes in version 0.2.1.10-alpha - 2009-01-06
+  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.
+
   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