aboutsummaryrefslogtreecommitdiff
path: root/changes
diff options
context:
space:
mode:
authorSebastian Hahn <sebastian@torproject.org>2010-03-01 22:26:44 +0100
committerSebastian Hahn <sebastian@torproject.org>2010-06-04 21:04:08 +0200
commitfaf51fa52a7462e356927ac521ff4e6ee0703d7c (patch)
treef67a570a6d54a6e616813204180b5f66ae7b011a /changes
parent7e300cbba36a0716b8d4ca6373ffbe372fca9713 (diff)
downloadtor-faf51fa52a7462e356927ac521ff4e6ee0703d7c.tar
tor-faf51fa52a7462e356927ac521ff4e6ee0703d7c.tar.gz
Don't cannibalize one-hop circuits
In rare cases, we could cannibalize a one-hop circuit, ending up with a two-hop circuit. This circuit would not be actually used, but we should prevent its creation in the first place. Thanks to outofwords and swissknife for helping to analyse this.
Diffstat (limited to 'changes')
-rw-r--r--changes/dont_cannibalize_onehop_circuits6
1 files changed, 6 insertions, 0 deletions
diff --git a/changes/dont_cannibalize_onehop_circuits b/changes/dont_cannibalize_onehop_circuits
new file mode 100644
index 000000000..10e5fe5f3
--- /dev/null
+++ b/changes/dont_cannibalize_onehop_circuits
@@ -0,0 +1,6 @@
+ o Refactorings:
+ - Make it explicit that we don't cannibalize one-hop circuits. This happens
+ in the wild, but doesn't turn out to be a problem because we fortunately
+ don't use those circuits. Many thanks to outofwords for the initial
+ analysis and to swissknife who confirmed that two-hop circuits are
+ actually created.