[tor-commits] [tor/release-0.2.2] fold in changes entries so far
arma at torproject.org
arma at torproject.org
Fri Apr 8 20:55:13 UTC 2011
commit 39cc300303993628afa1e067538cbd7d319f46b0
Author: Roger Dingledine <arma at torproject.org>
Date: Fri Apr 8 16:54:50 2011 -0400
fold in changes entries so far
---
ChangeLog | 36 ++++++++++++++++++++++++++++++++++++
changes/bug539_removal | 6 ------
changes/connect_err_reporting | 6 ------
changes/count_overflow | 5 -----
changes/feature2711 | 4 ----
changes/full_ap_circuits | 6 ------
changes/kill_ftime | 7 -------
changes/noroute | 5 -----
8 files changed, 36 insertions(+), 39 deletions(-)
diff --git a/ChangeLog b/ChangeLog
index 70afe71..ce68ccb 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,39 @@
+Changes in version 0.2.2.25-alpha - 2011-04-??
+ o Major features:
+ - Export GeoIP information on usage to bridge controller even if
+ we have not yet been running for 24 hours.
+
+ o Minor bugfixes:
+ - Be more careful about reporting the correct error from a failed
+ connect() system call. Under some circumstances, it was possible to
+ look at an incorrect value for errno when sending the end reason.
+ Bugfix on 0.1.0.1-rc.
+ - Correctly handle an "impossible" overflow cases in connection
+ byte counting, where we write or read more than 4GB on an edge
+ connection in single second. Bugfix on 0.1.2.8-beta.
+ - When a client finds that an origin circuit has run out of 16-bit
+ stream IDs, we now mark it as unusable for new streams. Previously,
+ we would try to close the entire circuit. Bugfix on Tor 0.0.6.
+
+ o Minor features:
+ - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
+ Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
+ clients are already deprecated because of security bugs.
+
+ o Code simplification and refactoring:
+ - Removed workaround code to handle directory responses from
+ servers that had bug 539 (they would send HTTP status 503
+ responses _and_ send a body too). Since only server versions before
+ 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason
+ to keep the workaround in place.
+ - Remove the old 'fuzzy time' logic. It was supposed to be used
+ for handling calculations where we have a known amount of clock
+ skew and an allowed amount of unknown skew. But we only used it
+ in three places, and we never adjusted the known/unknown skew
+ values. This is still something we might want to do someday,
+ but if we do, we'll want to do it differently.
+
+
Changes in version 0.2.2.24-alpha - 2011-04-08
Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
prevented Tor clients from effectively using "multihomed" bridges,
diff --git a/changes/bug539_removal b/changes/bug539_removal
deleted file mode 100644
index dbff43d..0000000
--- a/changes/bug539_removal
+++ /dev/null
@@ -1,6 +0,0 @@
- o Removed code
- - Removed workaround code to handle directory responses from
- servers that had bug 539 (they would send HTTP status 503
- responses _and_ send a body too). Since only server versions
- before 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer
- reason to keep the workaround in place.
diff --git a/changes/connect_err_reporting b/changes/connect_err_reporting
deleted file mode 100644
index 61a46b6..0000000
--- a/changes/connect_err_reporting
+++ /dev/null
@@ -1,6 +0,0 @@
- o Minor bugfixes:
- - Be more careful about reporting the correct error from a failed
- connect() operation. Under some circumstances, it was possible to
- look at an incorrect value for errno when sending the end reason.
- Bugfix on Tor-0.1.0.1-rc.
-
diff --git a/changes/count_overflow b/changes/count_overflow
deleted file mode 100644
index f302ff2..0000000
--- a/changes/count_overflow
+++ /dev/null
@@ -1,5 +0,0 @@
- o Minor bugfixes:
- - Correctly handle an "impossible" overflow cases in connection
- byte counting, where we write or read more than 4GB on an edge
- connection in single second. Bugfix on 0.1.2.8-beta.
-
diff --git a/changes/feature2711 b/changes/feature2711
deleted file mode 100644
index 7cdcfbf..0000000
--- a/changes/feature2711
+++ /dev/null
@@ -1,4 +0,0 @@
- o Minor features
- - Export GeoIP information on usage to bridge controller even if we have
- not yet been running for 24 hours.
-
diff --git a/changes/full_ap_circuits b/changes/full_ap_circuits
deleted file mode 100644
index 379a1a1..0000000
--- a/changes/full_ap_circuits
+++ /dev/null
@@ -1,6 +0,0 @@
- o Minor bugfixes
- - When a client finds that an origin circuit has run out of 16-bit
- stream IDs, we now mark it as unusable for new streams.
- Previously, we would try to close the entire circuit. Bugfix on
- Tor version 0.0.6.
-
diff --git a/changes/kill_ftime b/changes/kill_ftime
deleted file mode 100644
index 47f4769..0000000
--- a/changes/kill_ftime
+++ /dev/null
@@ -1,7 +0,0 @@
- o Code simplification and refactoring
- - Remove the old 'fuzzy time' logic. It was supposed to be used
- for handling calculations where we have a known amount of clock
- skew and an allowed amount of unknown skew. But we only used it
- in three places, and we never adjusted the known/unknown skew
- values. This is still something we might want to do someday,
- but if we do, we'll want to do it differently.
diff --git a/changes/noroute b/changes/noroute
deleted file mode 100644
index 644deec..0000000
--- a/changes/noroute
+++ /dev/null
@@ -1,5 +0,0 @@
- - Minor features
- - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
- Clients before 0.2.1.27 didn't handle NOROUTE correctly, but
- such clients are already deprecated because of security bugs.
-
More information about the tor-commits
mailing list