summaryrefslogtreecommitdiff
path: root/changes
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2011-03-13 15:47:59 -0400
committerRoger Dingledine <arma@torproject.org>2011-03-13 15:47:59 -0400
commit1a9d19e9728c21ffa37f2b751df8e8e97c1835d3 (patch)
tree654b11c2b1f97870642e81c71789687b2b0549e9 /changes
parent151ab614421eed48ba2f39518695b8ee08206904 (diff)
downloadtor-1a9d19e9728c21ffa37f2b751df8e8e97c1835d3.tar.gz
tor-1a9d19e9728c21ffa37f2b751df8e8e97c1835d3.zip
we're not reachable if we don't have a routerinfo yet
Diffstat (limited to 'changes')
-rw-r--r--changes/bug11729
1 files changed, 9 insertions, 0 deletions
diff --git a/changes/bug1172 b/changes/bug1172
new file mode 100644
index 0000000000..3abd7437f5
--- /dev/null
+++ b/changes/bug1172
@@ -0,0 +1,9 @@
+ 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.