diff options
author | Roger Dingledine <arma@torproject.org> | 2011-05-10 21:26:01 -0400 |
---|---|---|
committer | Roger Dingledine <arma@torproject.org> | 2011-05-10 21:26:01 -0400 |
commit | 75953f9b60406815c96e9b4d324133c31ad1a084 (patch) | |
tree | 143262629d2192f6ea9a44c837234ea226eb69f7 /changes/bug1172 | |
parent | 1855b4ebfdd63c0c3beeeed5eefb9b0c3f50a8bd (diff) | |
parent | 8a36f2125137dc31a0771a8eeac0f2bb8c1343d0 (diff) | |
download | tor-75953f9b60406815c96e9b4d324133c31ad1a084.tar.gz tor-75953f9b60406815c96e9b4d324133c31ad1a084.zip |
Merge branch 'maint-0.2.1' into release-0.2.1
Diffstat (limited to 'changes/bug1172')
-rw-r--r-- | changes/bug1172 | 9 |
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. |