summaryrefslogtreecommitdiff
path: root/changes
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2011-03-08 15:52:43 -0500
committerNick Mathewson <nickm@torproject.org>2011-03-08 15:52:43 -0500
commit0d78a16c3642f7538266e007da79c39860aac332 (patch)
tree5e342568b1f08b14318ddd3b3996aa1125d20787 /changes
parent9c72324ae85c3f2cc23fee7d383128fa239b36d0 (diff)
parent5a4f7fa1e48923730376c0a42121e4c3022eef3b (diff)
downloadtor-0d78a16c3642f7538266e007da79c39860aac332.tar.gz
tor-0d78a16c3642f7538266e007da79c39860aac332.zip
Merge remote branch 'sebastian/bug1035' into maint-0.2.2
Diffstat (limited to 'changes')
-rw-r--r--changes/bug103513
1 files changed, 13 insertions, 0 deletions
diff --git a/changes/bug1035 b/changes/bug1035
new file mode 100644
index 0000000000..3d86330e63
--- /dev/null
+++ b/changes/bug1035
@@ -0,0 +1,13 @@
+ o Minor features (authorities)
+ - Take altered router IP addresses and ORPorts into account when
+ determining router stability. Previously, if a router changed
+ its IP or ORPort, the authorities would not treat it as having
+ any downtime for the purposes of stability calculation, whereas
+ clients would experience downtime since the change could take a
+ while to propagate to them. Resolves issue 1035.
+ o Minor bugfixes (authorities)
+ - Try to be more robust to hops back in time when calculating
+ router stability. Previously, if a run of uptime or downtime
+ appeared to be negative, the calculation could give incorrect
+ results. Bugfix on 0.2.0.6-alpha.
+