summaryrefslogtreecommitdiff
path: root/changes/bug1810
diff options
context:
space:
mode:
authorSebastian Hahn <sebastian@torproject.org>2011-05-21 19:10:11 +0200
committerRoger Dingledine <arma@torproject.org>2011-05-21 16:08:21 -0400
commit3ff7925a7027b81cb9f14b0863972b4d4e5b46a4 (patch)
tree29d0fcd6fb70d09fd26fe23b255e677567cc8ac4 /changes/bug1810
parentb8ffb00cf1ddf4ff1b64335f8677d600a948fffc (diff)
downloadtor-3ff7925a7027b81cb9f14b0863972b4d4e5b46a4.tar.gz
tor-3ff7925a7027b81cb9f14b0863972b4d4e5b46a4.zip
Don't recreate descriptor on sighup
We used to regenerate our descriptor whenever we'd get a sighup. This was caused by a bug in options_transition_affects_workers() that would return true even if the options were exactly the same. Down the call path we'd call init_keys(), which made us make a new descriptor which the authorities would reject, and the node would subsequently fall out of the consensus. This patch fixes only the first part of this bug: options_transition_affects_workers() behaves correctly now. The second part still wants a fix.
Diffstat (limited to 'changes/bug1810')
-rw-r--r--changes/bug18106
1 files changed, 6 insertions, 0 deletions
diff --git a/changes/bug1810 b/changes/bug1810
new file mode 100644
index 0000000000..11e561f7cf
--- /dev/null
+++ b/changes/bug1810
@@ -0,0 +1,6 @@
+ o Major bugfixes:
+ - Don't decide to make a new descriptor when receiving a HUP signal.
+ This bug has caused a lot of relays to disappear from the consensus
+ periodically. Fixes the most common case of triggering bug 1810;
+ bugfix on 0.2.2.7-alpha.
+