aboutsummaryrefslogtreecommitdiff
path: root/ChangeLog
diff options
context:
space:
mode:
authorKarsten Loesing <karsten.loesing@gmx.net>2009-06-30 20:35:03 +0200
committerNick Mathewson <nickm@torproject.org>2009-07-02 10:00:28 -0400
commit3e6bb050dd46491ac044808782a489bdf0c23f6d (patch)
treec8967bf8b83e8a4af6a0432d4e9e4bcb7d8270aa /ChangeLog
parent0cbc0c463bcd5f3a80fe9388f778d4b6e09e0815 (diff)
downloadtor-3e6bb050dd46491ac044808782a489bdf0c23f6d.tar
tor-3e6bb050dd46491ac044808782a489bdf0c23f6d.tar.gz
Make an attempt to fix bug 1024.
The internal error "could not find intro key" occurs when we want to send an INTRODUCE1 cell over a recently finished introduction circuit and think we built the introduction circuit with a v2 hidden service descriptor, but cannot find the introduction key in our descriptor. My first guess how we can end up in this situation is that we are wrong in thinking that we built the introduction circuit based on a v2 hidden service descriptor. This patch checks if we have a v0 descriptor, too, and uses that instead.
Diffstat (limited to 'ChangeLog')
-rw-r--r--ChangeLog3
1 files changed, 3 insertions, 0 deletions
diff --git a/ChangeLog b/ChangeLog
index dc0f3a2e3..55f0f2c95 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -14,6 +14,9 @@ Changes in version 0.2.1.17-?? - 2009-??-??
our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
- Do not cap bandwidths reported by directory authorities; they are
already adjusted to reflect reality.
+ - When we can't find an intro key for a v2 hidden service descriptor,
+ fall back to the v0 hidden service descriptor and log a bug message.
+ Workaround for bug1024.
o Major features:
- Clients now use the bandwidth values in the consensus, rather than