[tor-commits] [tor/release-0.2.2] fold in changes files so far

arma at torproject.org arma at torproject.org
Mon Mar 14 21:28:56 UTC 2011


commit 704a27b029ac94e26e6e3695a292294c4d4905da
Author: Roger Dingledine <arma at torproject.org>
Date:   Mon Mar 14 17:28:38 2011 -0400

    fold in changes files so far
---
 ChangeLog                |   41 +++++++++++++++++++++++++++++++++++++++++
 changes/bug1172          |    9 ---------
 changes/bug2510          |    8 --------
 changes/bug2511          |    6 ------
 changes/bug2573          |    3 ---
 changes/bug2716          |    5 -----
 changes/hsdir_assignment |    8 --------
 7 files changed, 41 insertions(+), 39 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index bfa634c..c920dc4 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,44 @@
+Changes in version 0.2.2.24-alpha - 2011-0?-??
+  o Major bugfixes:
+    - Directory authorities now use data collected from their own
+      uptime observations when choosing whether to assign the HSDir flag
+      to relays, instead of trusting the uptime value the relay reports in
+      its descriptor. This change helps prevent an attack where a small
+      set of nodes with frequently-changing identity keys can blackhole
+      a hidden service. (Only authorities need upgrade; others will be
+      fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
+    - Fix a bug where bridge users who configure the non-canonical
+      address of a bridge automatically switch to its canonical
+      address. If a bridge listens at more than one address, it should be
+      able to advertise those addresses independently and any non-blocked
+      addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
+      bug 2510.
+    - If you configured Tor to use bridge A, and then quit and
+      configured Tor to use bridge B instead, it would happily continue
+      to use bridge A if it's still reachable. While this behavior is
+      a feature if your goal is connectivity, in some scenarios it's a
+      dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
+
+  o Minor bugfixes:
+    - When we restart our relay, we might get a successful connection
+      from the outside before we've started our reachability tests,
+      triggering a warning: "ORPort found reachable, but I have no
+      routerinfo yet. Failing to inform controller of success." This
+      bug was harmless unless Tor is running under a controller
+      like Vidalia, in which case the controller would never get a
+      REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
+      fixes bug 1172.
+    - When a relay has failed several reachability tests, directory
+      authorities are more accurate at recording when it became
+      unreachable, so we can in turn provide more accuracy at assigning
+      Stable, Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves
+      bug 2716.
+
+  o Packaging fixes:
+    - Create the /var/run/tor directory on startup on OpenSUSE if it is
+      not already created. Patch from Andreas Stieger. Fixes bug 2573.
+
+
 Changes in version 0.2.2.23-alpha - 2011-03-08
   Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
   they restart they don't lose their bandwidth capacity estimate. This
diff --git a/changes/bug1172 b/changes/bug1172
deleted file mode 100644
index 3abd743..0000000
--- a/changes/bug1172
+++ /dev/null
@@ -1,9 +0,0 @@
-  o Minor bugfixes:
-    - When we restart our relay, we might get a successful connection
-      from the outside before we've started our reachability tests,
-      triggering a warning: "ORPort found reachable, but I have no
-      routerinfo yet. Failing to inform controller of success." This
-      bug was harmless unless Tor is running under a controller
-      like Vidalia, in which case the controller would never get a
-      REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
-      fixes bug 1172.
diff --git a/changes/bug2510 b/changes/bug2510
deleted file mode 100644
index 2c3f613..0000000
--- a/changes/bug2510
+++ /dev/null
@@ -1,8 +0,0 @@
-  o Major bugfixes:
-    - Fix a bug where bridge users who configure the non-canonical
-      address of a bridge automatically switch to its canonical
-      address. If a bridge listens at more than one address, it should be
-      able to advertise those addresses independently and any non-blocked
-      addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
-      bug 2510.
-
diff --git a/changes/bug2511 b/changes/bug2511
deleted file mode 100644
index a27696a..0000000
--- a/changes/bug2511
+++ /dev/null
@@ -1,6 +0,0 @@
-  o Major bugfixes:
-    - If you configured Tor to use bridge A, and then quit and
-      configured Tor to use bridge B instead, it would happily continue
-      to use bridge A if it's still reachable. While this behavior is
-      a feature if your goal is connectivity, in some scenarios it's a
-      dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
diff --git a/changes/bug2573 b/changes/bug2573
deleted file mode 100644
index 7a2a802..0000000
--- a/changes/bug2573
+++ /dev/null
@@ -1,3 +0,0 @@
-  o Minor packaging issues
-    - Create the /var/run/tor directory on startup on OpenSUSE if it is
-      not already created.  Patch from Andreas Stieger.  Fixes bug 2573.
diff --git a/changes/bug2716 b/changes/bug2716
deleted file mode 100644
index 4663ed3..0000000
--- a/changes/bug2716
+++ /dev/null
@@ -1,5 +0,0 @@
-  o Minor features:
-    - When a relay has failed several reachability tests, be more accurate
-      at recording when it became unreachable, so we can in turn provide
-      more accuracy at assigning Stable, Guard, HSDir, etc flags. Bugfix
-      on 0.2.0.6-alpha. Resolves bug 2716.
diff --git a/changes/hsdir_assignment b/changes/hsdir_assignment
deleted file mode 100644
index 5c04b9b..0000000
--- a/changes/hsdir_assignment
+++ /dev/null
@@ -1,8 +0,0 @@
-  o Security fixes:
-    - Directory authorities now use data collected from rephist when
-      choosing whether to assign the HSDir flag to relays, instead of
-      trusting the uptime value the relay reports in its descriptor.
-      This helps prevent an attack where a small set of nodes with
-      frequently-changing identity keys can blackhole a hidden service.
-      (Only authorities need upgrade; others will be fine once they do.)
-      Bugfix on 0.2.0.10-alpha; fixes bug 2709.



More information about the tor-commits mailing list