summaryrefslogtreecommitdiff
path: root/changes/bug3019
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2011-05-15 12:46:26 -0400
committerNick Mathewson <nickm@torproject.org>2011-05-15 20:13:44 -0400
commit2b9c5ee301f705cbf69c725ca749d4ac752c06d3 (patch)
treec46ee28c4f21ce5810c70ac7ff85ca3778c284f9 /changes/bug3019
parentbc44393eb59a1d303314b4b646b4d815f4eadc22 (diff)
downloadtor-2b9c5ee301f705cbf69c725ca749d4ac752c06d3.tar.gz
tor-2b9c5ee301f705cbf69c725ca749d4ac752c06d3.zip
Preserve bridge download status across SETCONF, HUP
This code changes it so that we don't remove bridges immediately when we start re-parsing our configuration. Instead, we mark them all, and remove all the marked ones after re-parsing our bridge lines. As we add a bridge, we see if it's already in the list. If so, we just unmark it. This new behavior will lose the property we used to have that bridges were in bridge_list in the same order in which they appeared in the torrc. I took a quick look through the code, and I'm pretty sure we didn't actually depend on that anywhere. This is for bug 3019; it's a fix on 0.2.0.3-alpha.
Diffstat (limited to 'changes/bug3019')
-rw-r--r--changes/bug30194
1 files changed, 4 insertions, 0 deletions
diff --git a/changes/bug3019 b/changes/bug3019
new file mode 100644
index 0000000000..4df709fb3b
--- /dev/null
+++ b/changes/bug3019
@@ -0,0 +1,4 @@
+ o Minor bugfixes:
+ - Do not reset the bridge descriptor download status every time we
+ re-parse our configuration or get a configuration change. Fixes
+ bug 3019; bugfix on Tor 0.2.0.3-alpha.