summaryrefslogtreecommitdiff
path: root/changes/bug2297-related
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2012-03-30 15:20:06 -0400
committerNick Mathewson <nickm@torproject.org>2012-03-30 15:20:06 -0400
commit5193752ca88849878a0843cec1e81c6b4b05e550 (patch)
tree2e2de92d708917b628795cf35232ffedb7dc1617 /changes/bug2297-related
parent458718d4975661831fa21d9f2653932e17c1bae0 (diff)
downloadtor-5193752ca88849878a0843cec1e81c6b4b05e550.tar.gz
tor-5193752ca88849878a0843cec1e81c6b4b05e550.zip
Exits don't need to fetch certs for unknown authorities
When we started RefuseUnknownExits back in 0.2.2.11-alpha, we started making exits act like they cache directory info (since they need an up-to-date idea of who is really a router). But this included fetching needless (unrecognized) authorities' certs, which doesn't make any sense for them. This is related to, but not necessarily the same as, the issue that Ian reported for bug #2297. (This patch is based on a patch from a user who I believe has asked not to be named. If I'm wrong about that, please add the appropriate name onto the changelog.)
Diffstat (limited to 'changes/bug2297-related')
-rw-r--r--changes/bug2297-related6
1 files changed, 6 insertions, 0 deletions
diff --git a/changes/bug2297-related b/changes/bug2297-related
new file mode 100644
index 0000000000..3d9af110f3
--- /dev/null
+++ b/changes/bug2297-related
@@ -0,0 +1,6 @@
+ o Minor bugfixes:
+ - Exit nodes don't need to fetch certificates for authorities that
+ they don't recognize; only directory authorities, bridges, and
+ caches need to do that. Fix related to bug 2297; bugfix on
+ 0.2.2.11-alpha.
+