summaryrefslogtreecommitdiff
path: root/changes
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2011-04-07 12:03:04 -0400
committerNick Mathewson <nickm@torproject.org>2011-04-07 12:03:04 -0400
commitba0cd8094f8e6ae0113ad69958d9d0973bb1f2c3 (patch)
tree1debba1496513f76473c42cd910ffe86a074d9e1 /changes
parent118d8ffdcb74137a36d22928ce6f46897809391e (diff)
parentfc647832783cab352bebba63fe0210d7be395058 (diff)
downloadtor-ba0cd8094f8e6ae0113ad69958d9d0973bb1f2c3.tar.gz
tor-ba0cd8094f8e6ae0113ad69958d9d0973bb1f2c3.zip
Merge remote-tracking branch 'public/xxx_fixups' into maint-0.2.2
Conflicts: src/or/or.h
Diffstat (limited to 'changes')
-rw-r--r--changes/bug539_removal6
-rw-r--r--changes/connect_err_reporting6
-rw-r--r--changes/count_overflow5
-rw-r--r--changes/full_ap_circuits6
-rw-r--r--changes/kill_ftime7
-rw-r--r--changes/noroute5
6 files changed, 35 insertions, 0 deletions
diff --git a/changes/bug539_removal b/changes/bug539_removal
new file mode 100644
index 0000000000..dbff43de18
--- /dev/null
+++ b/changes/bug539_removal
@@ -0,0 +1,6 @@
+ 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
new file mode 100644
index 0000000000..61a46b6580
--- /dev/null
+++ b/changes/connect_err_reporting
@@ -0,0 +1,6 @@
+ 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
new file mode 100644
index 0000000000..f302ff2d71
--- /dev/null
+++ b/changes/count_overflow
@@ -0,0 +1,5 @@
+ 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/full_ap_circuits b/changes/full_ap_circuits
new file mode 100644
index 0000000000..379a1a1b73
--- /dev/null
+++ b/changes/full_ap_circuits
@@ -0,0 +1,6 @@
+ 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
new file mode 100644
index 0000000000..47f4769735
--- /dev/null
+++ b/changes/kill_ftime
@@ -0,0 +1,7 @@
+ 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
new file mode 100644
index 0000000000..644deec453
--- /dev/null
+++ b/changes/noroute
@@ -0,0 +1,5 @@
+ - 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.
+