[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[or-cvs] [tor/maint-0.2.2 3/3] Issues with router_get_by_nickname() (3)



Author: Robert Hogan <robert@xxxxxxxxxxxxxxx>
Date: Sun, 17 Oct 2010 15:12:25 +0100
Subject: Issues with router_get_by_nickname() (3)
Commit: 69a496ba9810f5065f55af558932e84152ce50bc

Add changes file
---
 changes/bug1859 |    9 +++++++++
 1 files changed, 9 insertions(+), 0 deletions(-)
 create mode 100644 changes/bug1859

diff --git a/changes/bug1859 b/changes/bug1859
new file mode 100644
index 0000000..5b139f3
--- /dev/null
+++ b/changes/bug1859
@@ -0,0 +1,9 @@
+  o Minor bugfixes:
+    - Bring the logic that gathers routerinfos and assesses the
+      acceptability of circuits into line. This prevents a Tor OP from getting
+      locked in a cycle of choosing its local OR as an exit for a path (due to
+      a .exit request) and then rejecting the circuit because its OR is not
+      listed yet. Also prevent Tor clients from using an OR running in the same
+      instance as an exit (due to a .exit request) if the OR does not meet the
+      same requirements expected of an OR running elsewhere.
+      Fixes bug 1859; bugfix on 0.2.0-alpha.
-- 
1.7.1